public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/38503] [4.4 regression] warnings from -isystem headers strikes back.
Date: Fri, 27 Feb 2009 10:33:00 -0000	[thread overview]
Message-ID: <20090227103340.12156.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38503-7667@http.gcc.gnu.org/bugzilla/>



------- Comment #22 from rguenther at suse dot de  2009-02-27 10:33 -------
Subject: Re:  [4.4 regression] warnings from -isystem
 headers strikes back.

On Fri, 27 Feb 2009, pluto at agmk dot net wrote:

> ------- Comment #21 from pluto at agmk dot net  2009-02-27 10:29 -------
> (In reply to comment #20)
> > Same issue.  Only possible fix is to not apply TBAA pruning to escaped
> > symbols, which will - well - basically disable TBAA.  Testcase:
> 
> waht about this testcase?
> the bug is marked as fixed but warnings are still present?

The original reported problem is gone.  The testcase below is unfixable.

> > inline void *operator new (__SIZE_TYPE__, void *__p) throw() { return __p; }
> > 
> > struct Y {
> >   Y() {}
> >   int i;
> > };
> > 
> > struct X {
> >   X() {}
> >   void construct(const Y& y)
> >   {
> >     new (&m_data[0]) Y(y);
> >   }
> >   template <class T>
> >   Y& get() { return reinterpret_cast<Y&>(m_data); }
> >   bool initialized;
> >   char m_data[sizeof (Y)];
> > };
> > 
> > X x;
> > 
> > void bar(const X&);
> > void foo(Y& y)
> > {
> >   x.get<Y>() = y;
> >   x.initialized = true;
> >   bar(x);
> > }
> > 
> 
> t.cpp: In member function 'Y& X::get() [with T = Y]':
> t.cpp:25:   instantiated from here
> t.cpp:15: warning: dereferencing type-punned pointer will break strict-aliasing
> rules
> t.cpp: In function 'void foo(Y&)':
> t.cpp:25: warning: dereferencing pointer '<anonymous>' does break
> strict-aliasing rules
> t.cpp:25: note: initialized from here
> 
> 
> 


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38503


  parent reply	other threads:[~2009-02-27 10:33 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-12 11:36 [Bug middle-end/38503] New: " pluto at agmk dot net
2008-12-12 11:38 ` [Bug middle-end/38503] " pluto at agmk dot net
2008-12-12 11:55 ` rguenth at gcc dot gnu dot org
2009-01-01  5:13 ` pinskia at gcc dot gnu dot org
2009-01-05 11:24 ` rguenth at gcc dot gnu dot org
2009-01-09 10:25 ` jakub at gcc dot gnu dot org
2009-01-09 19:52 ` pluto at agmk dot net
2009-01-12 13:54 ` rguenth at gcc dot gnu dot org
2009-01-12 15:01 ` pluto at agmk dot net
2009-01-12 15:11 ` pluto at agmk dot net
2009-01-12 15:16 ` rguenther at suse dot de
2009-01-14 16:48 ` rguenth at gcc dot gnu dot org
2009-01-14 18:29 ` pluto at agmk dot net
2009-01-14 20:50 ` rguenther at suse dot de
2009-01-23 16:53 ` rguenth at gcc dot gnu dot org
2009-01-24 15:56 ` rguenth at gcc dot gnu dot org
2009-01-24 17:00 ` rguenth at gcc dot gnu dot org
2009-01-24 17:50 ` rguenth at gcc dot gnu dot org
2009-01-24 17:50 ` rguenth at gcc dot gnu dot org
2009-01-27 10:43 ` rguenth at gcc dot gnu dot org
2009-01-27 10:43 ` rguenth at gcc dot gnu dot org
2009-01-30 17:32 ` hjl at gcc dot gnu dot org
2009-02-02  8:55 ` pluto at agmk dot net
2009-02-02 10:23 ` rguenth at gcc dot gnu dot org
2009-02-27 10:30 ` pluto at agmk dot net
2009-02-27 10:33 ` rguenther at suse dot de [this message]
2009-02-27 11:05 ` pluto at agmk dot net
2009-02-27 11:07 ` rguenth at gcc dot gnu dot org
2009-02-27 11:22 ` pluto at agmk dot net
2009-02-27 12:04 ` rguenther at suse dot de

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=20090227103340.12156.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).