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 (fwd)
Date: Tue, 19 Nov 2002 15:26:00 -0000	[thread overview]
Message-ID: <20021112154604.2672.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: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/8534: [mainline regression] When compiling qt contradicting
 aliasing class created for bitfield constructor (fwd)
Date: Tue, 12 Nov 2002 09:46:03 -0600 (CST)

 ---------- Forwarded message ----------
 From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
 To: Jan Hubicka <jh@suse.cz>
 
 
 > > 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?
 
 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!
 
 Regards
   Wolfgang
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:           bangerth@ticam.utexas.edu
                                www: http://www.ticam.utexas.edu/~bangerth
 
 
 


                 reply	other threads:[~2002-11-12 15:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20021112154604.2672.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: 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).