public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "d.g.gorbachev at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/61879] New: [4.10 Regression] GCC gives "note: non-delegitimized UNSPEC UNSPEC_GOTOFF (1) found in variable location"
Date: Tue, 22 Jul 2014 15:24:00 -0000	[thread overview]
Message-ID: <bug-61879-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61879

            Bug ID: 61879
           Summary: [4.10 Regression] GCC gives "note: non-delegitimized
                    UNSPEC UNSPEC_GOTOFF (1) found in variable location"
           Product: gcc
           Version: 4.10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: d.g.gorbachev at gmail dot com
            Target: i686-pc-linux-gnu

Created attachment 33172
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33172&action=edit
Testcase

GCC 4.10.0 20140720 (experimental).

$ gcc -S -march=pentium4 -g -O2 -fpie bug.c
bug.c: In function 'foo':
bug.c:11:5: note: non-delegitimized UNSPEC UNSPEC_GOTOFF (1) found in variable
location
 int foo(int *p)
     ^
bug.c:11:5: note: non-delegitimized UNSPEC UNSPEC_GOTOFF (1) found in variable
location

Appeared in 210914 < r <= 211358.


             reply	other threads:[~2014-07-22 15:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22 15:24 d.g.gorbachev at gmail dot com [this message]
2014-11-19 13:30 ` [Bug target/61879] [5 " rguenth at gcc dot gnu.org
2014-11-19 13:58 ` rguenth at gcc dot gnu.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=bug-61879-4@http.gcc.gnu.org/bugzilla/ \
    --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).