[Bug tree-optimization/92131] incorrect assumption that (ao >= 0) is always false

2019-10-16 Thread arigo at tunes dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92131 --- Comment #8 from Armin Rigo --- I'd like to point out that the problem only shows up with all the extra lines of code that appear unrelated: everything before the loop, and the first half of the loop itself (the switch-with-goto with cases 8

[Bug tree-optimization/92131] incorrect assumption that (ao >= 0) is always false

2019-10-16 Thread arigo at tunes dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92131 --- Comment #7 from Armin Rigo --- Created attachment 47056 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47056=edit made the example runnable Here is a main(). Compare: * gcc -Og foomin3.c foomin3main.c && a.out * gcc -O1 foomin3.c

[Bug tree-optimization/92131] incorrect assumption that (ao >= 0) is always false

2019-10-16 Thread arigo at tunes dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92131 --- Comment #2 from Armin Rigo --- Created attachment 47054 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47054=edit slightly different version, with comments showing the expected values

[Bug tree-optimization/92131] incorrect assumption that (ao >= 0) is always false

2019-10-16 Thread arigo at tunes dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92131 --- Comment #1 from Armin Rigo --- Comment on attachment 47053 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47053 creduce'd C source that miscompiles in -O>=1 BTW I just noticed that the reduced code is highly self-recursive, but that's

[Bug tree-optimization/92131] New: incorrect assumption that (ao >= 0) is always false

2019-10-16 Thread arigo at tunes dot org
P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: arigo at tunes dot org Target Milestone: --- Created attachment 47053 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47053=edit creduce'd C source that miscompiles in -O>=1 The attache

[Bug c/79973] atanh() constant-folds differently than it would evaluate at runtime

2017-03-09 Thread arigo at tunes dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79973 --- Comment #3 from Armin Rigo --- Indeed, thanks for the feedback.

[Bug c/79973] New: atanh() constant-folds differently than it would evaluate at runtime

2017-03-09 Thread arigo at tunes dot org
Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: arigo at tunes dot org Target Milestone: --- Created attachment 40930 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40930=edit reproducer, linux x86-64, gcc -lm atanh(x), wh

[Bug target/70734] __builtin_add_overflow emits poor code on x86-64

2016-04-20 Thread arigo at tunes dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70734 --- Comment #4 from Armin Rigo --- Ah, sorry about that; I only checked the 5.x branch. My mistake.

[Bug target/70734] New: __builtin_add_overflow emits poor code on x86-64

2016-04-20 Thread arigo at tunes dot org
Component: target Assignee: unassigned at gcc dot gnu.org Reporter: arigo at tunes dot org Target Milestone: --- Tested on gcc_5_branch: extern void abort(void); void f(int a, int b, int *r) { if (__builtin_add_overflow(a, b, r)) abort

[Bug c/69037] New: arrays of constants as function arguments misinterpreted

2015-12-24 Thread arigo at tunes dot org
Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: arigo at tunes dot org Target Milestone: --- The following occurs in `gcc_5_branch` but not in the 5.3.0 release tag. The C front-end misinterprets arrays of constants which are passed as function

[Bug c/66768] New: __seg_fs and __seg_gs: issue when adding address space support

2015-07-05 Thread arigo at tunes dot org
Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: arigo at tunes dot org Target Milestone: --- Created attachment 35913 -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=35913action=edit Input incorrectly compiled with gcc-5.1.0-patched

[Bug c/66768] __seg_fs and __seg_gs: issue when adding address space support

2015-07-05 Thread arigo at tunes dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66768 --- Comment #1 from Armin Rigo arigo at tunes dot org --- Update: found out that the %gs prefix is correctly present when I compile with gcc -O1 -fno-ivopts bug1.c -S. So ivopts might be the place to look.

[Bug c/66768] __seg_fs and __seg_gs: issue when adding address space support

2015-07-05 Thread arigo at tunes dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66768 --- Comment #2 from Armin Rigo arigo at tunes dot org --- Actually gcc -O1 -fno-tree-loop-optimize bug1.c -S also restores the %gs prefix. I suspect however that this flag implies -fno-ivopts, or something. I found no other -fno-xxx that, when