public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> 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 15:41:00 -0000 [thread overview] Message-ID: <20021112155607.8822.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/8534; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: Jan Hubicka <jh@suse.cz> Cc: 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:53:43 -0600 (CST) > > > on other systems. Perhaps you have disabled check? > > > > No, I just looked it up, but I haven't. > > > > I think I have to leave this to you then. Thanks for your cooperation > > anyway! > OK, I will to analyze it bit more. > I am quite puzzled why it reproduces on x86_64 only as the code path is > quite generic. Perhaps the wrong alias set leaks there from some > backend hook, but there are not many (only va_args fiddles aliasing as > far as I can remember) My machine is presently used up with different tasks, but if I find some spare cycles this afternoon, I'll retry with a clean build of gcc (--enable-checking is the default on the main branch, right?). Cheers Wolfgang ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth
next reply other threads:[~2002-11-12 15:56 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-19 15:41 Wolfgang Bangerth [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 12:46 Jan Hubicka 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=20021112155607.8822.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --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).