From: Jim Wilson <wilson@cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] two ICEs with current compiler
Date: Thu, 18 Jan 2001 00:39:49 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005071@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005066@msgid-missing>
>gcc -DSTDC_HEADERS=1 -I. -I. -I.. -O2 -I/usr/lib/glib/include -I/usr/X11R6/include -c gdkgl.c -fPIC -DPIC -o .libs/gdkgl.lo
>gdkgl.c: In function `gdk_gl_pixmap_unref':
>gdkgl.c:318: Internal compiler error in `clear_by_pieces', at expr.c:2335
>Please submit a full bug report.
>See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
For the first problem, the code is passing a pointer to an incomplete type
to __builtin_memset. Internally, gcc set the alignment of incomplete types
to 1 bit. __builtin_memset then fails because it doesn't know how to copy
anything with less then 8-bit (char) alignment.
This was fixed by changing the default alignment to the same as char.
2000-10-26 Nathan Sidwell <nathan@codesourcery.com>
* tree.c (make_node, case 't'): Set alignment to that of
char_type_node.
Index: tree.c
=================================RCS file: /cvs/cvsfiles/devo/gcc/tree.c,v
retrieving revision 1.197
diff -p -r1.197 tree.c
*** tree.c 2000/07/14 17:46:32 1.197
--- tree.c 2001/01/18 00:24:51
*************** make_node (code)
*** 1076,1082 ****
case 't':
TYPE_UID (t) = next_type_uid++;
! TYPE_ALIGN (t) = 1;
TYPE_USER_ALIGN (t) = 0;
TYPE_MAIN_VARIANT (t) = t;
TYPE_OBSTACK (t) = obstack;
--- 1076,1082 ----
case 't':
TYPE_UID (t) = next_type_uid++;
! TYPE_ALIGN (t) = char_type_node ? TYPE_ALIGN (char_type_node) : 0;
TYPE_USER_ALIGN (t) = 0;
TYPE_MAIN_VARIANT (t) = t;
TYPE_OBSTACK (t) = obstack;
next prev parent reply other threads:[~2001-01-18 0:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-17 19:54 [Linux-ia64] two ICEs with current compiler Bill Nottingham
2001-01-18 0:39 ` Jim Wilson [this message]
2001-01-18 0:56 ` Jim Wilson
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=marc-linux-ia64-105590693005071@msgid-missing \
--to=wilson@cygnus.com \
--cc=linux-ia64@vger.kernel.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