public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "khimov at altell dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/61526] relocation R_X86_64_PC32 in shared object with static and extern
Date: Tue, 17 Jun 2014 09:28:00 -0000	[thread overview]
Message-ID: <bug-61526-4-keKenlEXKi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61526-4@http.gcc.gnu.org/bugzilla/>

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

Roman Khimov <khimov at altell dot ru> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #2 from Roman Khimov <khimov at altell dot ru> ---
Just tried the fix for PR61012 and indeed, it solves the problem. Thanks.


  parent reply	other threads:[~2014-06-17  9:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-16 14:48 [Bug lto/61526] New: " khimov at altell dot ru
2014-06-17  9:00 ` [Bug lto/61526] " rguenth at gcc dot gnu.org
2014-06-17  9:28 ` khimov at altell dot ru [this message]
2014-07-21 16:00 ` sandra at codesourcery dot com
2014-07-21 16:17 ` 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-61526-4-keKenlEXKi@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).