public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Stan Shebs <shebs@apple.com>
To: Geert bosch <bosch@gnat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: ICE outputting unaligned fp constant on powerpc-apple-darwin5.1
Date: Thu, 22 Nov 2001 04:18:00 -0000	[thread overview]
Message-ID: <3C06D70A.4EA36154@apple.com> (raw)
In-Reply-To: <EF52EEE2-E529-11D5-8EFA-00039344BF4A@gnat.com>

Geert bosch wrote:
> 
> Compiler bootstraps fine, but fails with the following test case:
> > struct s {
> >   char c;
> >   double d;
> > };
> >
> > struct s t [] = { { 0, 0.0 } };
> 
> It hits an ICE in assemble_real, at varasm.c:2169:
> >   if (align < GET_MODE_ALIGNMENT (mode))
> >     abort ();

OK OK, I admit to being a dirty software hoarder!  We have some
local patches to fix several alignment problems, and apparently
this is one of them, because your example works fine in our latest
code.  The patches are intermingled with a - get ready to retch -
-malign-mac68k option that is needed by some very old code, and
we wanted to separate things before submitting.  But clearly we
need to do the separating sooner rather than later - sorry!

Stan

WARNING: multiple messages have this Message-ID
From: Stan Shebs <shebs@apple.com>
To: Geert bosch <bosch@gnat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: ICE outputting unaligned fp constant on powerpc-apple-darwin5.1
Date: Thu, 29 Nov 2001 16:47:00 -0000	[thread overview]
Message-ID: <3C06D70A.4EA36154@apple.com> (raw)
Message-ID: <20011129164700.5c8Gt32H-TiDmAN-Fop4SIhZlaaYebHe33a73UnlKZI@z> (raw)
In-Reply-To: <EF52EEE2-E529-11D5-8EFA-00039344BF4A@gnat.com>

Geert bosch wrote:
> 
> Compiler bootstraps fine, but fails with the following test case:
> > struct s {
> >   char c;
> >   double d;
> > };
> >
> > struct s t [] = { { 0, 0.0 } };
> 
> It hits an ICE in assemble_real, at varasm.c:2169:
> >   if (align < GET_MODE_ALIGNMENT (mode))
> >     abort ();

OK OK, I admit to being a dirty software hoarder!  We have some
local patches to fix several alignment problems, and apparently
this is one of them, because your example works fine in our latest
code.  The patches are intermingled with a - get ready to retch -
-malign-mac68k option that is needed by some very old code, and
we wanted to separate things before submitting.  But clearly we
need to do the separating sooner rather than later - sorry!

Stan

  reply	other threads:[~2001-11-30  0:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-22  3:40 Geert bosch
2001-11-22  4:18 ` Stan Shebs [this message]
2001-11-22  8:57   ` Phil Edwards
2001-11-29 17:58     ` Phil Edwards
2001-11-29 16:47   ` Stan Shebs
2001-11-29 16:33 ` Geert bosch

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=3C06D70A.4EA36154@apple.com \
    --to=shebs@apple.com \
    --cc=bosch@gnat.com \
    --cc=gcc@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).