public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/53853] FAIL: g++.dg/other/pr53811.C -std=gnu++* (internal compiler error)
Date: Fri, 06 Jul 2012 10:03:00 -0000	[thread overview]
Message-ID: <bug-53853-4-4kPETT8lc5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53853-4@http.gcc.gnu.org/bugzilla/>

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

Uros Bizjak <ubizjak at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |4.7.2

--- Comment #6 from Uros Bizjak <ubizjak at gmail dot com> 2012-07-06 10:02:38 UTC ---
Author: uros
Date: Fri Jul  6 10:00:11 2012
New Revision: 189315

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=189315
Log:
    PR target/53853
    * config/i386/i386.c (x86_output_mi_thunk): For CM_LARGE_PIC model,
    emit PIC sequence for fnaddr symbol reference in advance.


Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/i386/i386.c


  parent reply	other threads:[~2012-07-06 10:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-04 12:25 [Bug target/53853] New: " dominiq at lps dot ens.fr
2012-07-04 13:06 ` [Bug target/53853] " iains at gcc dot gnu.org
2012-07-05 12:07 ` ubizjak at gmail dot com
2012-07-05 12:10 ` ubizjak at gmail dot com
2012-07-05 14:07 ` dominiq at lps dot ens.fr
2012-07-06  7:45 ` ubizjak at gmail dot com
2012-07-06 10:03 ` ubizjak at gmail dot com [this message]
2012-07-10 17:54 ` uros at gcc dot gnu.org
2012-07-10 17:56 ` ubizjak at gmail dot com

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-53853-4-4kPETT8lc5@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).