--- Additional Comments From stefaandr at hotmail dot com 2005-05-31 10:13
---
For the sake of completeness. the error produced with the new testcase:
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: /esat/alexandria1/sderoeck/src/gcc/main/configure
--prefix=/esat
--- Additional Comments From stefaandr at hotmail dot com 2005-05-30 19:21
---
confirmed, I cannot reproduce with the given testcase either. But my original
source code still triggers a (possibly the same) bug. I've extracted a new
testcase:
struct M {
double data[16];
d
Component: tree-optimization
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: stefaandr at hotmail dot com
CC: gcc-bugs at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21734
--- Additional Comments From stefaandr at hotmail dot com 2005-01-07 23:31
---
If accepting floats just as integers is an extension, then why does the same
code compile without problems when using integers? (Static integer constants
also need a memory location right? Or don't
ld returned 1 exit status
--
Summary: static const float initialization ignored
Product: gcc
Version: 4.0.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
