public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Bernhard.Rosenkranzer at linaro dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug regression/67415] New: [5.1/5.2 Regression] -mcpu= breaks -print-file-name for ARM crosscompilers
Date: Mon, 31 Aug 2015 22:50:00 -0000	[thread overview]
Message-ID: <bug-67415-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 67415
           Summary: [5.1/5.2 Regression] -mcpu= breaks -print-file-name
                    for ARM crosscompilers
           Product: gcc
           Version: 5.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: regression
          Assignee: unassigned at gcc dot gnu.org
          Reporter: Bernhard.Rosenkranzer at linaro dot org
  Target Milestone: ---

If -mcpu=anything is specified on the gcc command line, -print-file-name stops
looking in the compiler's armv7-a library subdirectories.

$ gcc-5.2/bin/arm-linux-androideabi-gcc -print-file-name=libatomic.a
/MYPREFIX/gcc-5.2/bin/../lib/gcc/arm-linux-androideabi/5.2.1/../../../../arm-linux-androideabi/lib/armv7-a/libatomic.a

works as expected, but:

$ gcc-5.2/bin/arm-linux-androideabi-gcc -mcpu=cortex-a9
-print-file-name=libatomic.a
libatomic.a
$ gcc-5.2/bin/arm-linux-androideabi-gcc -mcpu=generic-armv7-a
-print-file-name=libatomic.a
libatomic.a

4.9 behaves as expected, 5.1 and 5.2 don't find the library.


             reply	other threads:[~2015-08-31 22:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31 22:50 Bernhard.Rosenkranzer at linaro dot org [this message]
2015-08-31 22:56 ` [Bug regression/67415] " Bernhard.Rosenkranzer at linaro dot org
2015-09-01  8:34 ` [Bug regression/67415] [5/6 " rguenth at gcc dot gnu.org
2015-09-01 14:57 ` rearnsha at gcc dot gnu.org
2015-09-02 17:09 ` Bernhard.Rosenkranzer at linaro dot org
2015-09-02 21:41 ` rearnsha 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-67415-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).