https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115274
D. Richard Hipp changed:
What|Removed |Added
CC||drh at sqlite dot org
--- Comment #6
: normal
Priority: P3
Component: ada
Assignee: unassigned at gcc dot gnu.org
Reporter: drh at sqlite dot org
CC: dkm at gcc dot gnu.org
Target Milestone: ---
Created attachment 55484
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96304
--- Comment #5 from D. Richard Hipp ---
((In reply to Martin Liška from comment #3)
> > But, are we violating aliasing rules here? What am I missing?
>
> Likely you are, but I must admit it's sometimes quite difficult to find that.
> From quick
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96304
--- Comment #2 from D. Richard Hipp ---
(In reply to Andrew Pinski from comment #1)
> Does -fno-strict-aliasing helps?
The problem goes away if I compile with -fno-strict-aliasing. I should have
thought to try that.
But, are we violating aliasi
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: drh at sqlite dot org
Target Milestone: ---
Gcc 8.3.0 appears to be miscompiling SQLite for ARM when using -O2. A correct
build occurs with any other optimization setting, on X86_64, and
Assignee: unassigned at gcc dot gnu.org
Reporter: drh at sqlite dot org
Target Milestone: ---
gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2), the Default install on ubuntu 20.04
A long long int varargs parameter goes in as 0xfff7 but comes out as
0x. In other words
--- Comment #3 from drh at sqlite dot org 2007-07-22 11:43 ---
Follow-up comments to the original bug report in SQLite
(see the link shown above) report that the same problem
exists in GCC 4.2.1. A work-around for SQLite was
devised, which was to change a single line of code
--- Comment #2 from drh at sqlite dot org 2007-07-01 22:52 ---
(In reply to comment #1)
> Can you at least provide the preprocessed source of vdbe.c ?
>
Certainly. But before I do, I just noticed that I gave the
wrong GCC version number in the bug report. The error is
in GCC
A bug reported against SQLite appears to be a case of GCC 4.3.0
miscompiling a single line of code within SQLite. The problem only
appears with -O2 or -Os. The problem goes away if we add the
-fno-tree-vrp option. The original bug report can be found at
http://www.sqlite.org/cvstrac/tktview?
