https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114855
--- Comment #8 from Andrew Macleod ---
(In reply to Andrew Macleod from comment #7)
> LOoks like the primary culprits now are:
>
> dominator optimization : 666.73 ( 7%) 0.77 ( 2%) 671.76 (
> 7%) 170M ( 4%)
> backwards jump
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114855
--- Comment #7 from Andrew Macleod ---
LOoks like the primary culprits now are:
dominator optimization : 666.73 ( 7%) 0.77 ( 2%) 671.76 ( 7%)
170M ( 4%)
backwards jump threading :7848.77 ( 85%) 21.04 (
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114855
Richard Biener changed:
What|Removed |Added
CC||aldyh at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114855
--- Comment #5 from jeremy rutman ---
Using gcc 14.0.1 20240117 (experimental) [master r14-8187-gb00be6f1576] I was
able to compile when not using any flags:
$ /usr/lib/gcc-snapshot/bin/cc -c aesDecrypt.c -o aesDecrypt.o
But when using the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114855
Richard Biener changed:
What|Removed |Added
CC||amacleod at redhat dot com
Ever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114855
--- Comment #3 from jeremy rutman ---
For what it's worth, clang is able to compile the code in question.
Ubuntu clang version 18.1.3 (1)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114855
--- Comment #2 from Andrew Pinski ---
The code basically does a bunch of:
const SWord8 s599 = s557 ? s595 : s598;
const SWord8 s600 = s561 ? 14 : 246;
const SWord8 s601 = s561 ? 3 : 72;
const SWord8 s602 = s559 ? s600 : s601;
const
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114855
--- Comment #1 from Andrew Pinski ---
Worthing noting on the trunk most of the compile time seems to be in the ranger
code ...
