chaforinli
chaforinli
I have run the following python program program1.py by codon. class Q625NBX (): TL331N2 = 0.77 syS0808 = 0.86 TaiXA3f9 = 28 HwexU9apV = 7886 def oDt49nu52 ( self )...
I have run the following python program program2.py by codon. class O8Y694p3o (): a3e16X35 = "CgtSETQBaCgC" def L62326a80a ( self , XY7C5a3Z : bytes ) -> bytes : if ((True)or(False))or((("sR2Kt7"))==(self.a3e16X35))...
I have run the following python program program3.py by codon. class g32Ck29 (): l618xA2v = "IXgotDE13" JR2F7RH5o = "r" ZPs35284 = 0.5 vggx3vQ3 = 0.31 def Q0400A8 ( self ,...
I have run the following python program program10.py by codon. class ZgM3gNx202 (): q1Z69u23 = 31 def eih319224 ( self ) : u0r65y5c8 = 6960 self.q1Z69u23/=(1if((1if(self.q1Z69u23==0)else(self.q1Z69u23))==0)else((1if(self.q1Z69u23==0)else(self.q1Z69u23)))) ; if __name__ ==...
### Summary When compiling a Rust program that attempts to add two very large arrays, GCCRS terminates with a fatal error (`gccrs: fatal error: Killed signal terminated program`), while Rustc...
### Summary When compiling a Rust program containing a macro that matches the meta fragment specifier, GCCRS exceeds the processing time limit and is terminated with SIGKILL. The same code...
### Summary When compiling the attached Rust code with GCCRS, the compiler gets terminated with SIGKILL due to processing time exceeded, while rustc correctly reports the missing Display trait implementation....
### Summary When compiling code containing match expressions with a macro-expanded tuple struct pattern (ApplicationTy(TypeCtor::X)) or equivalent OR patterns, gccrs fails to terminate and gets killed (SIGKILL). The same code...
### Summary When compiling code with deeply nested macro_rules! expansions (e.g., x10!{x10!{x10!{...}}}), GCCRS consumes excessive resources and gets killed by the OS (SIGKILL), while Rustc handles it gracefully. ### Reproducer...
### Summary When compiling the attached Rust code containing invalid nested inner attributes and delimiter mismatches, GCCRS enters an infinite loop or excessive resource consumption, leading to a SIGKILL termination....