public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "michael dot gurlitz at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/45298] New: GNATMake fails with multiple, equal -mcpu options
Date: Mon, 16 Aug 2010 13:42:00 -0000 [thread overview]
Message-ID: <bug-45298-19570@http.gcc.gnu.org/bugzilla/> (raw)
Passing a -mcpu=xxx option after a regular argument (a filename), when an
equivalent -mcpu=xxx option was specified earlier, causes gnatmake to fail:
$ gnatmake -mcpu=7400 hello -o hello.exe -bargs -mcpu=7400 rtems_init.o
Exception name: SYSTEM.ASSERTIONS.ASSERT_FAILURE
Message: make.adb:7473
gnatmake: INTERNAL ERROR. Please report.
$ powerpc-rtems4.11-gnatmake -mcpu=7400 hello -o hello.exe -bargs -mcpu=7400
rtems_init.o
Exception name: SYSTEM.ASSERTIONS.ASSERT_FAILURE
Message: make.adb:7473
gnatmake: INTERNAL ERROR. Please report.
Removing either -mcpu=7400 option allows for compilation, and the resulting
executable works. I found this bug when compiling an RTEMS sample program which
for some reason specified many arguments twice (-bargs, -D__ppc_generic, etc.).
However, I believe that issue was related to my environment at the time, since
I haven't been able to recreate it.
--
Summary: GNATMake fails with multiple, equal -mcpu options
Product: gcc
Version: 4.5.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ada
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: michael dot gurlitz at gmail dot com
GCC build triplet: i386-pc-solaris2.10
GCC host triplet: i386-pc-solaris2.10
GCC target triplet: i386-pc-solaris2.10, powerpc-rtems4.11
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45298
next reply other threads:[~2010-08-16 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 13:42 michael dot gurlitz at gmail dot com [this message]
2010-08-16 13:44 ` [Bug ada/45298] " michael dot gurlitz at gmail dot com
2010-08-16 14:05 ` michael dot gurlitz 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-45298-19570@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).