public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave at hiauly1 dot hia dot nrc dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/20493] [4.0/4.1 Regression] Bootstrap failure because of aliased symbols
Date: Fri, 18 Mar 2005 02:33:00 -0000 [thread overview]
Message-ID: <20050318023314.20022.qmail@sourceware.org> (raw)
In-Reply-To: <20050316054704.20493.danglin@gcc.gnu.org>
------- Additional Comments From dave at hiauly1 dot hia dot nrc dot ca 2005-03-18 02:33 -------
Subject: Re: [4.0/4.1 Regression] Bootstrap failure because of aliased symbols
> Hmm, yep, probably caused by my change.
Confirmed.
> It looks like with my change fold_widened_comparison is now converting
> (int)t == -1 into the equivalent t == (typeof(t))-1. Normally, this
> would be reasonable but the "special" semantics of
> HAVE_canonical_funcptr_for_compare clearly screw this up.
The bootstrap still fails with your suggestion. fold_widened_comparison
returns here:
if (arg0_unw == arg0)
return NULL_TREE;
as the function pointer is not being widen by the int cast of the
function pointer.
It seems that it's the change to tree.c that causing the problem.
However, there might still be a problem with fold_widened_comparison
if the cast had been to long long.
Dave
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20493
next prev parent reply other threads:[~2005-03-18 2:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 5:47 [Bug bootstrap/20493] New: [4.0 Regression] Bootstrap failure danglin at gcc dot gnu dot org
2005-03-16 6:26 ` [Bug middle-end/20493] " pinskia at gcc dot gnu dot org
2005-03-16 6:42 ` pinskia at gcc dot gnu dot org
2005-03-16 6:43 ` pinskia at gcc dot gnu dot org
2005-03-16 14:38 ` dave at hiauly1 dot hia dot nrc dot ca
2005-03-16 14:43 ` dave at hiauly1 dot hia dot nrc dot ca
2005-03-17 3:13 ` danglin at gcc dot gnu dot org
2005-03-17 5:02 ` [Bug middle-end/20493] [4.0/4.1 Regression] Bootstrap failure because of aliased symbols pinskia at gcc dot gnu dot org
2005-03-17 5:08 ` roger at eyesopen dot com
2005-03-18 2:33 ` dave at hiauly1 dot hia dot nrc dot ca [this message]
2005-03-18 3:26 ` dave at hiauly1 dot hia dot nrc dot ca
2005-03-19 16:46 ` cvs-commit at gcc dot gnu dot org
2005-03-19 17:30 ` cvs-commit at gcc dot gnu dot org
2005-03-19 17:38 ` danglin at gcc dot gnu dot org
2005-03-19 17:52 ` pinskia at gcc dot gnu dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050318023314.20022.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).