public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: antti-pekka.virjonen@computec.fi
To: gcc-gnats@gcc.gnu.org
Subject: other/5372: GCC 3.0.3: Target: powerpc-*-eabi, -mno-eabi not working
Date: Mon, 14 Jan 2002 02:06:00 -0000	[thread overview]
Message-ID: <20020114100553.27512.qmail@sources.redhat.com> (raw)


>Number:         5372
>Category:       other
>Synopsis:       GCC 3.0.3: Target: powerpc-*-eabi, -mno-eabi not working
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jan 14 02:06:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     antti-pekka.virjonen@computec.fi
>Release:        GCC-3.0.3
>Organization:
>Environment:
Cygwin (current) under Win2K
>Description:
GCC-3.0.3 cross compiler for powerpc-*-eabi running under
Cygwin slightly illbehaves. When used with the -mno-eabi
option, the compiler still generates a call to the __eabi
function. According to the Gcc man-page, this should not
happen. Otherwise the -mno-eabi -option seems to work ok 
(stack alignment changes like it should).

The older compiler (Gcc egcs-2.91.66 under Linux (Redhat 7.1))
works ok in this respect (though it seems to handle these
things differently).

Pretty easy to get around this is to add a void __eabi()
function in the application code... but it would be
nice if it worked correctly out of box.

Regards,
Antti-Pekka
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2002-01-14 10:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020114100553.27512.qmail@sources.redhat.com \
    --to=antti-pekka.virjonen@computec.fi \
    --cc=gcc-gnats@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).