public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Weiwen Liu <liu@hepvms.physics.yale.edu>
To: egcs-bugs@cygnus.com
Subject: optimization bug
Date: Fri, 19 Sep 1997 21:03:00 -0000	[thread overview]
Message-ID: <Pine.OSF.3.96.970911163700.19871A-100000@ylws32> (raw)

Hi,

On alpha-dec-osf4.0, egcs-2.90.08 970917 fails to compile the following
program with -O2 or -O3, but succeeds with -O1. 
The error message:
gcc: Internal compiler error: program cc1 got fatal signal 11

Weiwen

/* tmp.i */
enum Lisp_Type
{
  Lisp_Int                     
  ,Lisp_Record                 
  ,Lisp_Cons                   
  ,Lisp_String                 
  ,Lisp_Vector                 
  ,Lisp_Symbol
  ,Lisp_Char			 
};
typedef
union Lisp_Object
{
    struct
    {
	unsigned long  type_mark: 3L  + 1;
	signed long  val: (((8 * 8 ) )-((3L )+1L)) ;
    } s;
    struct
    {
        enum Lisp_Type type: 3L ;
	unsigned long  markbit: 1;
	unsigned long  val: (((8 * 8 ) )-((3L )+1L)) ;
    } gu;
    long  i;
    struct __nosuchstruct__ *v;
    struct __nosuchstruct__ *cv;              
}
Lisp_Object;
extern Lisp_Object pure[]; 
int
purified (Lisp_Object obj)
{
    if (! (( ((enum Lisp_Type) (  obj  ).gu.type)   ) != Lisp_Int
           && ( ((enum Lisp_Type) (  obj  ).gu.type)   ) != Lisp_Char) )
        return (0);
    return (((unsigned long ) ( ((void *) (( obj ).gu.val))  )
             <	(unsigned long ) (((unsigned char *) pure)
                                  + ((((1400000 ) + (43000 ) + (43000 )
                                       + (4000 ) + (4000 ) + (95000 )
                                       + (99000) + (100000 )) )) )
             &&	(unsigned long ) ( ((void *) (( obj ).gu.val))  )
             >=	(unsigned long ) ((unsigned char *) pure) ) );
}





             reply	other threads:[~1997-09-19 21:03 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-09-19 21:03 Weiwen Liu [this message]
1997-09-21 18:07 Weiwen Liu
1997-09-21 21:28 ` Jeffrey A Law
1997-09-21 21:28   ` Weiwen Liu
1997-09-22 11:08     ` Jeffrey A Law
1997-09-22 22:55       ` Jim Wilson
1997-09-23 13:08         ` Jim Wilson
1997-09-24  7:51           ` Weiwen Liu
1997-11-02 22:26 ` Jeffrey A Law
1998-10-12 11:18 Optimization bug Phillip Ezolt
1999-01-13  5:41 ` Jeffrey A Law
1998-10-22 10:56 optimization bug Dima Volodin
1998-10-25 12:17 ` Valentin Bonnard
1998-10-25 17:41   ` Dima Volodin
1998-10-26 18:00     ` Alexandre Oliva
1998-10-27  8:56       ` Dima Volodin
1998-10-27 11:04         ` Alexandre Oliva
1998-10-27  9:54           ` Dima Volodin
1998-10-25 21:47 Kaoru Fukui
1998-10-27 11:04 Valentin Bonnard
1999-03-31 23:54 Optimization bug Hyman Rosen
1999-03-31 23:54 ` Jeffrey A Law
1999-03-31 23:54   ` Hyman Rosen
1999-12-31 20:54 Peter R. Torpman
1999-12-31 20:54 ` Nathan Sidwell
2000-03-22  1:41 optimization bug Andrea Latina
2000-03-24 12:07 Optimization bug Gerald Gutierrez
     [not found] <20000812004418.A4935@a2000.nl>
2000-08-12  9:30 ` Richard Henderson
2002-01-04  6:20 optimization bug Calin Cascaval
2003-03-10 14:24 surjan
2003-03-10 15:31 ` Tim Prince

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=Pine.OSF.3.96.970911163700.19871A-100000@ylws32 \
    --to=liu@hepvms.physics.yale.edu \
    --cc=egcs-bugs@cygnus.com \
    /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).