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 other/31359] 4.2 branch still generates abort for function casting
Date: Mon, 26 Mar 2007 05:02:00 -0000	[thread overview]
Message-ID: <20070326050146.27184.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31359-10406@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from pinskia at gcc dot gnu dot org  2007-03-26 06:01 -------
Can you show the exact code from openssl which has the problem, there might be
better ways of writting the code instead of what they are doing right now. 
This code is still undefined and I don't think we really should change the
behavior of GCC to be a behavior of code which is undefined.  Before we would
crash on some of the undefined behavior but now we don't and we warn more
places where the undefined behavior happens so that is even better thing.  At
least we don't sliently cause the undefined behavior to be crash (which is
actually valid for the C standard).

I rather see openssl fix their code than GCC change the behavior, it is not
like they were depending on defined behavior and GCC causes defined behavior to
become undefined.  Also if we say this was an "undocumented extension", I think
that is wrong as there is no such thing as an undocumented extension, just it
worked because GCC did not fail before.


-- 


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


  reply	other threads:[~2007-03-26  5:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-26  4:33 [Bug other/31359] New: " dirtyepic at gentoo dot org
2007-03-26  5:02 ` pinskia at gcc dot gnu dot org [this message]
2007-03-26  9:14 ` [Bug other/31359] " rguenth at gcc dot gnu dot org
2007-03-26 13:27 ` dirtyepic at gentoo dot org
2007-03-26 16:19 ` pinskia at gcc dot gnu dot org
2007-03-27  0:50 ` dirtyepic at gentoo dot org
2008-01-08 18:36 ` manu 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=20070326050146.27184.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).