public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Jan Hubicka <jh@suse.cz> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/8534: [mainline regression] When compiling qt contradicting aliasing class created for bitfield constructor Date: Tue, 19 Nov 2002 12:46:00 -0000 [thread overview] Message-ID: <20021112082601.22486.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/8534; it has been noted by GNATS. From: Jan Hubicka <jh@suse.cz> To: Wolfgang Bangerth <bangerth@ticam.utexas.edu> Cc: jh@suse.cz, gcc-gnats@gcc.gnu.org Subject: Re: c++/8534: [mainline regression] When compiling qt contradicting aliasing class created for bitfield constructor Date: Tue, 12 Nov 2002 09:17:07 +0100 > Hi, > Hi Jan, > am I correct that PRs 8533 and 8534 are duplicates? If so, I can close one Uhm yes, 8533 is duplicate, I will close it and mark 8535 as high priority. > of these. Also, I cannot reproduce them on a different system, so I don't > think it's a front end problem. Shall I re-group them as "middle-end" or > "optimization"? I am not sure. Definitly frontend decides the aliasing classes that are contradicting in this testcase. I am not sure why it does not reproduce on other systems. Perhaps you have disabled check? I will try to figure out from where the alias sets are constructed at the evening. Honza > > Regards > Wolfgang > > ------------------------------------------------------------------------- > Wolfgang Bangerth email: bangerth@ticam.utexas.edu > www: http://www.ticam.utexas.edu/~bangerth >
next reply other threads:[~2002-11-12 8:26 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-19 12:46 Jan Hubicka [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-19 15:56 Jan Hubicka 2002-11-19 15:48 Wolfgang Bangerth 2002-11-19 15:46 Jan Hubicka 2002-11-19 15:41 Wolfgang Bangerth 2002-11-19 12:46 Wolfgang Bangerth 2002-11-19 12:23 jh
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=20021112082601.22486.qmail@sources.redhat.com \ --to=jh@suse.cz \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).