From: Joseph Myers <joseph@codesourcery.com>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>,
<gcc-patches@gcc.gnu.org>, <rguenther@suse.de>
Subject: Re: Teach gimple_canonical_types_compatible_p about incomplete types
Date: Mon, 01 Jun 2015 19:47:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.10.1506011942040.18155@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20150529225626.GA24506@kam.mff.cuni.cz>
On Sat, 30 May 2015, Jan Hubicka wrote:
> Joseph, does the attached testcase make sense for you? Is it defined? It is my
> first attempt to really interpret C standard to detail.
I suppose it's defined if unsigned int is the type chosen as compatible
with that enum. The test should be skipped for short_enums targets
(arm-eabi bare metal) (you can't simply use -fno-short-enums as then that
will fail the link-time compatibility checking).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2015-06-01 19:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 1:32 Jan Hubicka
2015-05-25 17:33 ` Bernhard Reutner-Fischer
2015-05-26 1:18 ` Jan Hubicka
2015-05-29 21:37 ` Joseph Myers
2015-05-29 21:46 ` Jan Hubicka
2015-05-30 3:28 ` Jan Hubicka
2015-05-30 15:38 ` Bernhard Reutner-Fischer
2015-05-30 21:14 ` Jan Hubicka
2015-06-01 19:47 ` Joseph Myers [this message]
2015-06-02 17:34 ` Jan Hubicka
2015-06-02 17:43 ` Joseph Myers
2015-06-02 17:55 ` Jan Hubicka
2015-06-03 11:41 ` Richard Biener
2015-06-03 22:12 ` Jan Hubicka
2015-05-26 8:45 ` Richard Biener
2015-05-26 17:36 ` Jan Hubicka
2015-05-27 8:38 ` Richard Biener
2015-05-27 22:53 ` Jan Hubicka
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=alpine.DEB.2.10.1506011942040.18155@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=rep.dot.nop@gmail.com \
--cc=rguenther@suse.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).