[Bug target/69073] internal compiler error: in maybe_record_trace_start

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69073 --- Comment #7 from Yoshinori Sato --- Created attachment 52308 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52308&action=edit comment 4 reproduce source

[Bug target/69073] internal compiler error: in maybe_record_trace_start

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69073 --- Comment #6 from Yoshinori Sato --- I got same ICE on following gcc. ❯ rx-unknown-linux-gcc --version rx-unknown-linux-gcc (GCC) 12.0.0 20210903 (experimental) ❯ rx-unknown-linux-gcc -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs -fno

[Bug target/97431] [SH] Python crashes with 'Segmentation fault with -finline-small-functions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97431 --- Comment #2 from Yoshinori Sato --- Since 0x296318e8 is data, we need to investigate where we jumped. The backtrace looks normal, so I think you're getting anomalous jumps when optimizing long_richcompare.