From: "Terry Guo" <terry.guo@arm.com>
To: <gcc-patches@gcc.gnu.org>
Cc: <ro@cebitec.uni-bielefeld.de>
Subject: RE: [Patch, gcc, testsuite] Use long enums for case foldconst-3.c for target ARM EABI.
Date: Fri, 16 Sep 2011 08:16:00 -0000 [thread overview]
Message-ID: <000001cc7444$65bd1370$31373a50$@guo@arm.com> (raw)
In-Reply-To:
Ping.
BR,
Terry
> -----Original Message-----
> From: Terry Guo [mailto:terry.guo@arm.com]
> Sent: Sunday, September 11, 2011 9:39 AM
> To: gcc-patches@gcc.gnu.org
> Cc: ro@cebitec.uni-bielefeld.de
> Subject: [Patch, gcc, testsuite] Use long enums for case foldconst-3.c
> for target ARM EABI.
>
> Hello,
>
> This patch aims to disable short enums for arm eabi otherwise the case
> will
> fail to be compiled due to "width of 'code' exceeds its type". Is it OK
> to
> trunk?
>
> BR,
> Terry
>
> 2011-09-09 Terry Guo <terry.guo@arm.com>
>
> * gcc.dg/tree-ssa/foldconst-3.c: Use -fno-short-enums
> for ARM EABI target.
>
> diff --git a/gcc/testsuite/gcc.dg/tree-ssa/foldconst-3.c
> b/gcc/testsuite/gcc.dg/tree-ssa/foldconst-3.c
> index 6132362..e030f53 100644
> --- a/gcc/testsuite/gcc.dg/tree-ssa/foldconst-3.c
> +++ b/gcc/testsuite/gcc.dg/tree-ssa/foldconst-3.c
> @@ -1,5 +1,6 @@
> /* { dg-do compile } */
> /* { dg-options "-O2 -fdump-tree-optimized" } */
> +/* { dg-options "-O2 -fdump-tree-optimized -fno-short-enums" { target
> arm_eabi } } */
> typedef const union tree_node *const_tree;
> typedef struct
> {
>
>
next reply other threads:[~2011-09-16 7:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 8:16 Terry Guo [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-09-11 2:42 Terry Guo
2011-09-16 8:30 ` Richard Earnshaw
2011-09-16 9:17 ` Terry Guo
2011-09-16 10:45 ` Richard Earnshaw
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='000001cc7444$65bd1370$31373a50$@guo@arm.com' \
--to=terry.guo@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ro@cebitec.uni-bielefeld.de \
/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).