public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/47500] New: mips-*-rtems*: -G0 option not recognized by gnat1
Date: Thu, 27 Jan 2011 22:53:00 -0000	[thread overview]
Message-ID: <bug-47500-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: mips-*-rtems*: -G0 option not recognized by gnat1
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: ada
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: joel@gcc.gnu.org


The checking for arguments passed to gnat1 does not allow for -Gn which is used
on at least the mips.  

$ mips-rtems4.11-gcc -c -march=r3900  -G0 -fstack-check -O -O2
-I/users/joel/test-gcc/gcc-svn/gcc/testsuite/ada/acats/work-jmr3904/support
a22006b.adb
Usage: gnat1 switches sfile

  sfile     Source file name

..................

$ mips-rtems4.11-gcc -c -march=r3900  -fstack-check -O -O2
-I/users/joel/test-gcc/gcc-svn/gcc/testsuite/ada/acats/work-jmr3904/support
a22006b.adb

This switch is meaningful on at least the MIPS and PowerPC.  

`-G NUM'
     On embedded PowerPC systems, put global and static items less than
     or equal to NUM bytes into the small data or bss sections instead
     of the normal data or bss section.  By default, NUM is 8.  The `-G
     NUM' switch is also passed to the linker.  All modules should be
     compiled with the same `-G NUM' value.

I thought that adding 'G' to the list around line 204 of switch-m.adb
would have addressed it but I must not be looking in the right place.

Hints or tiny patch appreciated.


             reply	other threads:[~2011-01-27 22:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-27 22:53 joel at gcc dot gnu.org [this message]
2011-01-28  9:26 ` [Bug ada/47500] " ebotcazou at gcc dot gnu.org
2011-01-28 18:08 ` joel at gcc dot gnu.org
2011-01-28 20:58 ` pinskia at gcc dot gnu.org
2011-01-28 22:46 ` joel at gcc dot gnu.org
2011-01-30 23:41 ` ebotcazou at gcc dot gnu.org
2011-09-05 19:45 ` [Bug target/47500] " linux at schildmann dot info
2014-11-06 23:11 ` ebotcazou at gcc dot gnu.org
2014-11-20 11:56 ` charlet at gcc dot gnu.org
2014-11-20 11:57 ` charlet at gcc dot gnu.org
2014-11-22 11:29 ` ebotcazou at gcc dot gnu.org
2014-11-22 11:30 ` ebotcazou at gcc dot gnu.org
2014-11-22 11:30 ` ebotcazou 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-47500-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).