https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118836
--- Comment #2 from George Thopas ---
(In reply to Andrew Pinski from comment #1)
> This is by design; without -fno-builtin, memcmp, memset, etc. become normal
> functions and they have unknown behaviors.
The only solution to get rid of the war
Assignee: unassigned at gcc dot gnu.org
Reporter: george.thopas at gmail dot com
Target Milestone: ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100920 introduced some logic
to suppress scalar-storage-order warnings when using memcpy/memset/...
However when required to compile
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: george.thopas at gmail dot com
Target Milestone: ---
/*
reversed storage order when compiling with -O3 only.
this time sets up an all big-endian struct
from an all little-endian one
no warnings
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100653
--- Comment #9 from George Thopas ---
Created attachment 51025
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51025&action=edit
avoid eliminating fields with different endianess as equal
Short story :
Ran a bisect to find why this always
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100920
--- Comment #9 from George Thopas ---
/*
Hi Eric,
1) I noticed there's a typo in the test, (which is my fault) and may give
unexpected behavior later on
memcpy(msg2, &msg1, sizeof(t_s12));
=> should be memcpy(msg2, msg1, sizeof(t_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100920
--- Comment #6 from George Thopas ---
(In reply to Eric Botcazou from comment #5)
> Thanks for reporting the problem.
Thanks for the swift fix. It nicely resolves it for the malloc/alloca ...
It doesn't seem to do anything for the rest of the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100920
--- Comment #2 from George Thopas ---
(In reply to Eric Botcazou from comment #1)
> The warning on the union is indeed an oversight, but the other is
> conservatively correct, although we may make a special case for
> __builtin_alloca.
Hi Eric,
Assignee: unassigned at gcc dot gnu.org
Reporter: george.thopas at gmail dot com
Target Milestone: ---
/*
* trying to use -Wscalar-storage-order on latest git version
*
* https://gcc.gnu.org/g:401bd4adcfda9965363b1ac3ba7e1580f15d6883
*
* below test exposes what looks like 2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100804
--- Comment #2 from George Thopas ---
After looking at the updated documentation and trying the an update kernel with
warning it still leaves some things open.
The updated documentation says:
"Moreover, the use of type punning or aliasing to
Assignee: unassigned at gcc dot gnu.org
Reporter: george.thopas at gmail dot com
Target Milestone: ---
/*
Target: x86_64-pc-linux-gnu gcc versie 10.2.0 (Gentoo 10.2.0-r4 p5)
failing:
$ gcc -Wall -Wextra -O2 test.c && ./a.out
Aborted
passing:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87623
--- Comment #9 from George Thopas ---
(In reply to Eric Botcazou from comment #8)
> Thanks for reporting the problem.
And thanks for the swift resolution !
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: george.thopas at gmail dot com
Target Milestone: ---
Target: x86_64-pc-linux-gnu
Build: gcc version 8.2.0 (Gentoo 8.2.0-r3 p1.4
12 matches
Mail list logo
