From: Jakub Jelinek <jakub@redhat.com>
To: Terry Guo <terry.guo@arm.com>
Cc: gcc-patches@gcc.gnu.org, ro@CeBiTec.Uni-Bielefeld.DE,
mikestump@comcast.net
Subject: Re: [Patch, testsuite] Skip case struct-layout-1 for targets using short enums.
Date: Thu, 01 Sep 2011 06:46:00 -0000 [thread overview]
Message-ID: <20110901064600.GO2687@tyan-ft48-01.lab.bos.redhat.com> (raw)
In-Reply-To: <000a01cc6870$fc7edc60$f57c9520$@guo@arm.com>
On Thu, Sep 01, 2011 at 02:32:51PM +0800, Terry Guo wrote:
> FAIL: gcc.dg/compat/struct-layout-1 c_compat_x_tst.o compile
> FAIL: gcc.dg/compat/struct-layout-1 c_compat_y_tst.o compile
> UNRESOLVED: gcc.dg/compat/struct-layout-1 c_compat_x_tst.o-c_compat_y_tst.o
> link
> UNRESOLVED: gcc.dg/compat/struct-layout-1 c_compat_x_tst.o-c_compat_y_tst.o
> execute
>
> On my machine, the error message is "error: width of 'a' exceeds its type".
> My GCC is cross built for arm-none-eabi based on upstream GCC 4.6. The
> command I run this case is simply as: "make check-gcc
> RUNTESTFLAGS="--target_board=arm-none-eabi-qemu/-mthumb/-mcpu=cortex-m3
> compat.exp=struct-layout-1*". Are there anything else I should do to pass
> this case?
Look into gcc/testsuite/gcc/gcc.log, search for struct-layout-1_generate.exe
and see whether -e has been passed to it? If not, debug the tcl bits which
are supposed to pass it, but for some reason don't, if yes, look into the
generator under debugger why it generates the large enum bitfield bitsizes
anyway (you can cut'n'paste the *generate.exe command line, compile it with
-g and rerun it under debugger...).
Jakub
next prev parent reply other threads:[~2011-09-01 6:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 1:40 Terry Guo
2011-09-01 6:14 ` Jakub Jelinek
2011-09-01 6:34 ` Terry Guo
2011-09-01 6:46 ` Jakub Jelinek [this message]
2011-09-01 7:10 ` Terry Guo
2011-09-01 7:23 ` Jakub Jelinek
2011-09-01 7:46 ` Terry Guo
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=20110901064600.GO2687@tyan-ft48-01.lab.bos.redhat.com \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikestump@comcast.net \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
--cc=terry.guo@arm.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).