public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/28718] Call to -lgcc added prior to user libraries
Date: Wed, 05 Sep 2012 13:02:00 -0000	[thread overview]
Message-ID: <bug-28718-4-YDIg3TrM7S@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-28718-4@http.gcc.gnu.org/bugzilla/>

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

Georg-Johann Lay <gjl at gcc dot gnu.org> changed:

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

--- Comment #12 from Georg-Johann Lay <gjl at gcc dot gnu.org> 2012-09-05 13:02:24 UTC ---
Not really a doublicate of PR54461, but the new configure option --with-avrlibc
introduced in 4.7.2 solves the issue by removing the doublicate functions from
libgcc so that the optimized versions from AVR-Libc will be used no matter how
the -l order is.

*** This bug has been marked as a duplicate of bug 54461 ***


  parent reply	other threads:[~2012-09-05 13:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-28718-4@http.gcc.gnu.org/bugzilla/>
2011-11-21 16:46 ` gjl at gcc dot gnu.org
2011-11-28 20:39 ` j at uriah dot heep.sax.de
2012-09-05 13:02 ` gjl at gcc dot gnu.org [this message]
2012-09-05 15:08 ` j at uriah dot heep.sax.de
2012-09-05 21:35 ` gjl at gcc dot gnu.org
2014-02-16 13:12 ` jackie.rosen at hushmail dot com
2006-08-14 12:13 [Bug c++/28718] New: " j at uriah dot heep dot sax dot de
2009-08-19 15:32 ` [Bug driver/28718] " abnikant dot singh at atmel 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-28718-4-YDIg3TrM7S@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).