public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/19058] [4.0 Regression] setjmp: 4.0 fails to give 'clobbered' warning (regression from 3.4.1)
Date: Wed, 02 Feb 2005 07:13:00 -0000	[thread overview]
Message-ID: <20050202071257.16874.qmail@sourceware.org> (raw)
In-Reply-To: <20041217160338.19058.bh@techhouse.brown.edu>


------- Additional Comments From rth at gcc dot gnu dot org  2005-02-02 07:12 -------
The warning has *always* been specifically dependant on which registers are
assigned to which decls.  So it was never assured that you'd get the warning
when you actually needed it.

In this case you're doubly screwed because you expect gcc to magically follow
the path from "*x" through the signal handler, through to setjmp.  Well, we're
not going to do that.

INVALID or WONTFIX, your choice.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |WONTFIX


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


      parent reply	other threads:[~2005-02-02  7:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-17 16:03 [Bug c/19058] New: " bh at techhouse dot brown dot edu
2004-12-17 16:18 ` [Bug c/19058] " pinskia at gcc dot gnu dot org
2004-12-20  0:56 ` [Bug tree-optimization/19058] [4.0 Regression] " pinskia at gcc dot gnu dot org
2004-12-20  0:56 ` [Bug tree-optimization/19058] " pinskia at gcc dot gnu dot org
2005-01-15  8:25 ` [Bug tree-optimization/19058] [4.0 Regression] " pinskia at gcc dot gnu dot org
2005-01-18  0:43 ` pinskia at gcc dot gnu dot org
2005-02-02  7:13 ` rth at gcc dot gnu dot org [this message]

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