* [Bug tree-optimization/30666] warning: canonical types differ for identical types double __complex__ and double __complex__
2007-02-01 13:57 [Bug tree-optimization/30666] New: warning: canonical types differ for identical types double __complex__ and double __complex__ ubizjak at gmail dot com
@ 2007-02-01 13:59 ` ubizjak at gmail dot com
2007-02-01 20:03 ` [Bug tree-optimization/30666] [4.3 Regression] " pinskia at gcc dot gnu dot org
` (11 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: ubizjak at gmail dot com @ 2007-02-01 13:59 UTC (permalink / raw)
To: gcc-bugs
------- Comment #1 from ubizjak at gmail dot com 2007-02-01 13:59 -------
Created an attachment (id=12993)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12993&action=view)
testcase
Testcase, compile with gcc -O2.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30666
^ permalink raw reply [flat|nested] 14+ messages in thread* [Bug tree-optimization/30666] [4.3 Regression] warning: canonical types differ for identical types double __complex__ and double __complex__
2007-02-01 13:57 [Bug tree-optimization/30666] New: warning: canonical types differ for identical types double __complex__ and double __complex__ ubizjak at gmail dot com
2007-02-01 13:59 ` [Bug tree-optimization/30666] " ubizjak at gmail dot com
@ 2007-02-01 20:03 ` pinskia at gcc dot gnu dot org
2007-02-22 11:04 ` ubizjak at gmail dot com
` (10 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2007-02-01 20:03 UTC (permalink / raw)
To: gcc-bugs
------- Comment #2 from pinskia at gcc dot gnu dot org 2007-02-01 20:03 -------
And this is the reason why it needs to be an ICE earlier because we don't see
these bugs until late.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|warning: canonical types |[4.3 Regression] warning:
|differ for identical types |canonical types differ for
|double __complex__ and |identical types double
|double __complex__ |__complex__ and double
| |__complex__
Target Milestone|--- |4.3.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30666
^ permalink raw reply [flat|nested] 14+ messages in thread* [Bug tree-optimization/30666] [4.3 Regression] warning: canonical types differ for identical types double __complex__ and double __complex__
2007-02-01 13:57 [Bug tree-optimization/30666] New: warning: canonical types differ for identical types double __complex__ and double __complex__ ubizjak at gmail dot com
2007-02-01 13:59 ` [Bug tree-optimization/30666] " ubizjak at gmail dot com
2007-02-01 20:03 ` [Bug tree-optimization/30666] [4.3 Regression] " pinskia at gcc dot gnu dot org
@ 2007-02-22 11:04 ` ubizjak at gmail dot com
2007-02-22 12:21 ` rguenth at gcc dot gnu dot org
` (9 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: ubizjak at gmail dot com @ 2007-02-22 11:04 UTC (permalink / raw)
To: gcc-bugs
------- Comment #3 from ubizjak at gmail dot com 2007-02-22 11:04 -------
These warnirngs disappear by commenting out TARGET_HAS_SINCOS in
config/linux.h.
These warnings indeed point to pov::create_ray, where we have quite some tree
sincos transformations:
int pov::create_ray(pov::RAY*, double, double, int) (Ray, x, y, ray_number)
{
complex double sincostmp.447;
complex double sincostmp.446;
complex double sincostmp.445;
complex double sincostmp.444;
complex double sincostmp.443;
complex double sincostmp.442;
complex double sincostmp.441;
complex double sincostmp.440;
complex double sincostmp.439;
complex double sincostmp.438;
complex double sincostmp.437;
I'm adding Richard Guenther to the CC as he worken on tree sincos
transformation a while ago.
--
ubizjak at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rguenth at gcc dot gnu dot
| |org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30666
^ permalink raw reply [flat|nested] 14+ messages in thread* [Bug tree-optimization/30666] [4.3 Regression] warning: canonical types differ for identical types double __complex__ and double __complex__
2007-02-01 13:57 [Bug tree-optimization/30666] New: warning: canonical types differ for identical types double __complex__ and double __complex__ ubizjak at gmail dot com
` (2 preceding siblings ...)
2007-02-22 11:04 ` ubizjak at gmail dot com
@ 2007-02-22 12:21 ` rguenth at gcc dot gnu dot org
2007-02-22 17:21 ` [Bug middle-end/30666] " pinskia at gcc dot gnu dot org
` (8 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: rguenth at gcc dot gnu dot org @ 2007-02-22 12:21 UTC (permalink / raw)
To: gcc-bugs
------- Comment #4 from rguenth at gcc dot gnu dot org 2007-02-22 12:21 -------
Dough - how is the middle-end supposed to handle this? The case in question
get's a
double sin(double)
and wants to build
_Complex double cexpi(double)
It now uses tree.c:build_complex_type which seems to fix TYPE_CANONICAL in some
way.
--
rguenth at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |doug dot gregor at gmail dot
| |com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30666
^ permalink raw reply [flat|nested] 14+ messages in thread* [Bug middle-end/30666] [4.3 Regression] warning: canonical types differ for identical types double __complex__ and double __complex__
2007-02-01 13:57 [Bug tree-optimization/30666] New: warning: canonical types differ for identical types double __complex__ and double __complex__ ubizjak at gmail dot com
` (3 preceding siblings ...)
2007-02-22 12:21 ` rguenth at gcc dot gnu dot org
@ 2007-02-22 17:21 ` pinskia at gcc dot gnu dot org
2007-02-26 15:27 ` doug dot gregor at gmail dot com
` (7 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2007-02-22 17:21 UTC (permalink / raw)
To: gcc-bugs
------- Comment #5 from pinskia at gcc dot gnu dot org 2007-02-22 17:21 -------
There is also code in build_common_tree_nodes_2 which needs changed to use
build_complex_type which also could be causing issues too.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pinskia at gcc dot gnu dot
| |org
Component|tree-optimization |middle-end
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30666
^ permalink raw reply [flat|nested] 14+ messages in thread* [Bug middle-end/30666] [4.3 Regression] warning: canonical types differ for identical types double __complex__ and double __complex__
2007-02-01 13:57 [Bug tree-optimization/30666] New: warning: canonical types differ for identical types double __complex__ and double __complex__ ubizjak at gmail dot com
` (4 preceding siblings ...)
2007-02-22 17:21 ` [Bug middle-end/30666] " pinskia at gcc dot gnu dot org
@ 2007-02-26 15:27 ` doug dot gregor at gmail dot com
2007-03-02 15:38 ` ubizjak at gmail dot com
` (6 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: doug dot gregor at gmail dot com @ 2007-02-26 15:27 UTC (permalink / raw)
To: gcc-bugs
------- Comment #6 from doug dot gregor at gmail dot com 2007-02-26 15:26 -------
This looks like a straightforward fix to build_common_tree_nodes2.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30666
^ permalink raw reply [flat|nested] 14+ messages in thread* [Bug middle-end/30666] [4.3 Regression] warning: canonical types differ for identical types double __complex__ and double __complex__
2007-02-01 13:57 [Bug tree-optimization/30666] New: warning: canonical types differ for identical types double __complex__ and double __complex__ ubizjak at gmail dot com
` (5 preceding siblings ...)
2007-02-26 15:27 ` doug dot gregor at gmail dot com
@ 2007-03-02 15:38 ` ubizjak at gmail dot com
2007-03-03 19:50 ` patchapp at dberlin dot org
` (5 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: ubizjak at gmail dot com @ 2007-03-02 15:38 UTC (permalink / raw)
To: gcc-bugs
------- Comment #7 from ubizjak at gmail dot com 2007-03-02 15:37 -------
(In reply to comment #6)
> This looks like a straightforward fix to build_common_tree_nodes2.
Is it possible to provide a patch for this? This warning is generated during
povray compilation, and povray is part of SPEC2006 package.
(I'm self-confirming the bug, as the problem can be shown by compiling attached
testcase.)
--
ubizjak at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2007-03-02 15:37:59
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30666
^ permalink raw reply [flat|nested] 14+ messages in thread* [Bug middle-end/30666] [4.3 Regression] warning: canonical types differ for identical types double __complex__ and double __complex__
2007-02-01 13:57 [Bug tree-optimization/30666] New: warning: canonical types differ for identical types double __complex__ and double __complex__ ubizjak at gmail dot com
` (6 preceding siblings ...)
2007-03-02 15:38 ` ubizjak at gmail dot com
@ 2007-03-03 19:50 ` patchapp at dberlin dot org
2007-03-03 19:50 ` doug dot gregor at gmail dot com
` (4 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: patchapp at dberlin dot org @ 2007-03-03 19:50 UTC (permalink / raw)
To: gcc-bugs
------- Comment #9 from patchapp at dberlin dot org 2007-03-03 19:50 -------
Subject: Bug number PR 30666
A patch for this bug has been added to the patch tracker.
The mailing list url for the patch is
http://gcc.gnu.org/ml/gcc-patches/2007-03/msg00191.html
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30666
^ permalink raw reply [flat|nested] 14+ messages in thread* [Bug middle-end/30666] [4.3 Regression] warning: canonical types differ for identical types double __complex__ and double __complex__
2007-02-01 13:57 [Bug tree-optimization/30666] New: warning: canonical types differ for identical types double __complex__ and double __complex__ ubizjak at gmail dot com
` (7 preceding siblings ...)
2007-03-03 19:50 ` patchapp at dberlin dot org
@ 2007-03-03 19:50 ` doug dot gregor at gmail dot com
2007-03-28 14:30 ` dgregor at gcc dot gnu dot org
` (3 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: doug dot gregor at gmail dot com @ 2007-03-03 19:50 UTC (permalink / raw)
To: gcc-bugs
------- Comment #8 from doug dot gregor at gmail dot com 2007-03-03 19:50 -------
Patch is here: http://gcc.gnu.org/ml/gcc-patches/2007-03/msg00191.html
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30666
^ permalink raw reply [flat|nested] 14+ messages in thread* [Bug middle-end/30666] [4.3 Regression] warning: canonical types differ for identical types double __complex__ and double __complex__
2007-02-01 13:57 [Bug tree-optimization/30666] New: warning: canonical types differ for identical types double __complex__ and double __complex__ ubizjak at gmail dot com
` (8 preceding siblings ...)
2007-03-03 19:50 ` doug dot gregor at gmail dot com
@ 2007-03-28 14:30 ` dgregor at gcc dot gnu dot org
2007-03-29 13:26 ` patchapp at dberlin dot org
` (2 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: dgregor at gcc dot gnu dot org @ 2007-03-28 14:30 UTC (permalink / raw)
To: gcc-bugs
--
dgregor at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |dgregor at gcc dot gnu dot
|dot org |org
Status|NEW |ASSIGNED
Last reconfirmed|2007-03-02 15:37:59 |2007-03-28 15:30:33
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30666
^ permalink raw reply [flat|nested] 14+ messages in thread* [Bug middle-end/30666] [4.3 Regression] warning: canonical types differ for identical types double __complex__ and double __complex__
2007-02-01 13:57 [Bug tree-optimization/30666] New: warning: canonical types differ for identical types double __complex__ and double __complex__ ubizjak at gmail dot com
` (9 preceding siblings ...)
2007-03-28 14:30 ` dgregor at gcc dot gnu dot org
@ 2007-03-29 13:26 ` patchapp at dberlin dot org
2007-03-29 14:12 ` dgregor at gcc dot gnu dot org
2007-03-29 14:14 ` dgregor at gcc dot gnu dot org
12 siblings, 0 replies; 14+ messages in thread
From: patchapp at dberlin dot org @ 2007-03-29 13:26 UTC (permalink / raw)
To: gcc-bugs
------- Comment #10 from patchapp at dberlin dot org 2007-03-29 14:25 -------
Subject: Bug number PR 30666
A patch for this bug has been added to the patch tracker.
The mailing list url for the patch is
http://gcc.gnu.org/ml/gcc-patches/2007-03/msg01939.html
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30666
^ permalink raw reply [flat|nested] 14+ messages in thread* [Bug middle-end/30666] [4.3 Regression] warning: canonical types differ for identical types double __complex__ and double __complex__
2007-02-01 13:57 [Bug tree-optimization/30666] New: warning: canonical types differ for identical types double __complex__ and double __complex__ ubizjak at gmail dot com
` (10 preceding siblings ...)
2007-03-29 13:26 ` patchapp at dberlin dot org
@ 2007-03-29 14:12 ` dgregor at gcc dot gnu dot org
2007-03-29 14:14 ` dgregor at gcc dot gnu dot org
12 siblings, 0 replies; 14+ messages in thread
From: dgregor at gcc dot gnu dot org @ 2007-03-29 14:12 UTC (permalink / raw)
To: gcc-bugs
------- Comment #11 from dgregor at gcc dot gnu dot org 2007-03-29 15:11 -------
Subject: Bug 30666
Author: dgregor
Date: Thu Mar 29 15:11:28 2007
New Revision: 123330
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=123330
Log:
2007-03-29 Douglas Gregor <doug.gregor@gmail.com>
PR tree-optimization/30666
* tree.c (build_complex_type): When creating type names for DWARF2
debug info, create TYPE_DECLs for TYPE_NAME instead of
IDENTIFIER_NODEs.
(build_common_tree_nodes_2): Use build_complex_type when building
predefined complex types, to preserve canonical types.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/tree.c
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30666
^ permalink raw reply [flat|nested] 14+ messages in thread* [Bug middle-end/30666] [4.3 Regression] warning: canonical types differ for identical types double __complex__ and double __complex__
2007-02-01 13:57 [Bug tree-optimization/30666] New: warning: canonical types differ for identical types double __complex__ and double __complex__ ubizjak at gmail dot com
` (11 preceding siblings ...)
2007-03-29 14:12 ` dgregor at gcc dot gnu dot org
@ 2007-03-29 14:14 ` dgregor at gcc dot gnu dot org
12 siblings, 0 replies; 14+ messages in thread
From: dgregor at gcc dot gnu dot org @ 2007-03-29 14:14 UTC (permalink / raw)
To: gcc-bugs
------- Comment #12 from dgregor at gcc dot gnu dot org 2007-03-29 15:14 -------
Fix committed to mainline
--
dgregor at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30666
^ permalink raw reply [flat|nested] 14+ messages in thread