https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100788
Bug ID: 100788
Summary: Internal compiler error related to #line macros(?)
Product: gcc
Version: 11.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100788
--- Comment #1 from seberg ---
Created attachment 50875
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50875&action=edit
preprocessed_file
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100788
--- Comment #3 from seberg ---
Created attachment 50878
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50878&action=edit
actual_preprocessed_with_gcc
Sorry, I think this is what you are looking for now, adding -E to it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100788
--- Comment #5 from seberg ---
> Now I miss the command line.
Do you mean more than the failing call?:
x86_64-linux-gnu-gcc -pthread --coverage -O0 -ggdb -g
-ffile-prefix-map=/build/python3.9-RNBry6/python3.9-3.9.2=.
-fstack-protector-strong -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100788
--- Comment #7 from seberg ---
Oh, interesting. You are right, if I run it on the preprocessed file it
succeeds (note the `tmp/preprocessed.c`:
x86_64-linux-gnu-gcc -pthread --coverage -O0 -ggdb -g
-ffile-prefix-map=/build/python3.9-RNBry6/pyt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100788
--- Comment #9 from seberg ---
NumPy is pretty light weight (at least on linux systems, and if you do not care
about setting up BLAS manually). You probably only need the Python dev
headers, that I expect you already have.
Hopefully, the follo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100788
--- Comment #11 from seberg ---
Does that mean that fixing the `#line` directives (or inserting additional
ones) should be able to fix the issue? (Or work around it, if you consider it
a bug.)
I tried to figure out where the `#line` directives
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105480
Bug ID: 105480
Summary: Vectorized `isnan` appears to trigger FPE on ppc64le
Product: gcc
Version: 11.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Comp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105480
--- Comment #1 from seberg ---
Actually, I think I likely misanalyzed, the actual code in question where I
found this was doing something like:
while (n--) {
if (isnan(*input)) {
*out = 1;
}
else {
*out = (long
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105480
--- Comment #2 from seberg ---
I still owed the correct example: https://godbolt.org/z/33Pj6xvPr
Now I think the cause is the indeed (somewhat understandandable) desire to
optimize away the branching. And not the instruction (I am not sure how
10 matches
Mail list logo
