public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/25152] [3.4/4.0 only] no warning from -Wstrict-aliasing for C++ code
Date: Thu, 08 Dec 2005 15:43:00 -0000	[thread overview]
Message-ID: <20051208154323.5502.qmail@sourceware.org> (raw)
In-Reply-To: <bug-25152-11785@http.gcc.gnu.org/bugzilla/>



------- Comment #9 from pinskia at gcc dot gnu dot org  2005-12-08 15:43 -------
(In reply to comment #8)
> For 4.0, it is IMHO a bad idea to backport this, there are tons of programs
> built with -Werror and if we suddenly start issuing a huge amount of new
> warnings (and this warning has sometimes many false positives), we'd force
> people to change packages a lot.  People are used to do this kind of things
> when porting to a newer major GCC version, but e.g. when upgrading from
> x.y.z to x.y.z+1 it is not expected.

They might not be expecting this.  The warning has very few false warnings.

Actually they are broken (in fact they don't know what hit them in 4.0.x).  In
fact 4.0.x already uses strict aliasing information more than 3.4.0.  I also
have seen 3.4.x use strict aliasing more than 3.3.3 did too.


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2005-12-08 15:43:23
               date|                            |
            Summary|[4.0 only] no warning from -|[3.4/4.0 only] no warning
                   |Wstrict-aliasing for C++    |from -Wstrict-aliasing for
                   |code                        |C++ code
   Target Milestone|4.1.0                       |4.0.3


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


  parent reply	other threads:[~2005-12-08 15:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-29 13:28 [Bug c++/25152] New: -fstrict-aliasing generates wrong code, but no warning from -Wstrict-aliasing frederic dot devernay at m4x dot org
2005-11-29 13:30 ` [Bug c++/25152] " frederic dot devernay at m4x dot org
2005-11-29 15:12 ` pinskia at gcc dot gnu dot org
2005-11-29 17:42 ` frederic dot devernay at m4x dot org
2005-11-29 17:47 ` pinskia at gcc dot gnu dot org
2005-11-29 17:55 ` bonzini at gnu dot org
2005-11-30 16:02 ` drow at gcc dot gnu dot org
2005-11-30 16:06 ` [Bug c++/25152] [4.0/4.1 only] " pinskia at gcc dot gnu dot org
2005-12-08 12:30 ` [Bug c++/25152] [4.0 only] no warning from -Wstrict-aliasing for C++ code jakub at gcc dot gnu dot org
2005-12-08 15:43 ` pinskia at gcc dot gnu dot org [this message]
2006-01-15 22:50 ` [Bug c++/25152] [3.4/4.0 " mmitchel 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=20051208154323.5502.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).