public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rschiele@uni-mannheim.de
To: gcc-gnats@gcc.gnu.org
Subject: target/7839: Misaligned stack in expand_call() on i386, i486 and i586
Date: Thu, 05 Sep 2002 10:46:00 -0000	[thread overview]
Message-ID: <20020905174138.5304.qmail@sources.redhat.com> (raw)


>Number:         7839
>Category:       target
>Synopsis:       Misaligned stack in expand_call() on i386, i486 and i586
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Thu Sep 05 10:46:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Robert Schiele
>Release:        3.2.1 20020904 (prerelease) and 3.3 20020904 (experimental)
>Organization:
>Environment:
System: Linux vodalia 2.4.18-4GB #1 Tue Jul 30 07:43:42 UTC 2002 i686 unknown
Architecture: i686
host: i486-suse-linux-gnu
build: i486-suse-linux-gnu
target: i486-suse-linux-gnu
configured with: /home/schiele/gcccvs/gcc.gcc-3_2-branch/configure --enable-threads=posix --prefix=/opt/Pkg/Linux/i686/gcc321 --enable-languages=c,c++,f77,objc --disable-libgcj --with-gxx-include-dir=/opt/Pkg/Linux/i686/gcc321/include/g++ --with-system-zlib --enable-shared --enable-__cxa_atexit i486-suse-linux
>Description:
On compiling the attached file with -march={i386,i486,i586} I get the following:

# gcc -march=i586 -c ice.ii
ice.ii: In member function `B D<<anonymous> >::a(B) [with int <anonymous> =
   0]':
ice.ii:16:   instantiated from here
ice.ii:10: Internal compiler error in expand_call, at calls.c:3049
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.

This does not happen with -march >= i686.
>How-To-Repeat:
gcc -march=i586 -c ice.ii
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/x-c++src; name="ice.ii"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="ice.ii"

Y2xhc3MgQiB7CiAgICB2b2lkKiBhOwogICAgd2NoYXJfdCBiOwogICAgY2hhciBjOwp9OwoKdGVt
cGxhdGUgPGludD4gc3RydWN0IEQgewogICAgQiBhKEIgYikgewoJd2NoYXJfdCBlOwoJZyhiLCBi
LCAwLCBlLCBlKTsKICAgIH0KfTsKCnRlbXBsYXRlIDxjbGFzcyBCLCBjbGFzcyBDLCBjbGFzcyBB
PiB2b2lkIGcoQiYsIEIsIEMsIEEsIEEpOwoKdGVtcGxhdGUgY2xhc3MgRDwwPjsK


             reply	other threads:[~2002-09-05 17:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-05 10:46 rschiele [this message]
2002-10-03 10:25 hubicka

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=20020905174138.5304.qmail@sources.redhat.com \
    --to=rschiele@uni-mannheim.de \
    --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).