public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/99212] [11 Regression] gcc.dg/analyzer/data-model-1.c line 971
Date: Fri, 09 Apr 2021 23:11:49 +0000	[thread overview]
Message-ID: <bug-99212-4-YVfdFyGcv3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99212-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99212

--- Comment #9 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #8)
> xfail/pass depending on sizeof (int) might be possible but as said it might
> be that cris doesn't have sizeof (int) == 1

You meant something else here than what you wrote.  If you meant (effectively)
sizeof (int) == 4, then "every port" has INT_TYPE_SIZE 32 (bits), including
those mentioned in this PR.

> but instead just lays out
> struct ubits in a way to have its size being 1.

It's true that sizeof (struct ubits) == 1 (byte) for cris-elf.

FWIW, I don't know what it is that pru-elf, cris-elf and m68k-linux have in
common that matters here.  First I was dead sure it was they got "#define
PCC_BITFIELD_TYPE_MATTERS false" but that doesn't seem to grep to true for
pru-elf.  cris-elf and m68k include config/elfos.h then #undef
PCC_BITFIELD_TYPE_MATTERS, so you get the quoted defaults.h line, but pru
doesn't have the #undef.

  parent reply	other threads:[~2021-04-09 23:11 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23  3:35 [Bug analyzer/99212] New: " hp at gcc dot gnu.org
2021-02-23  8:27 ` [Bug analyzer/99212] " rguenth at gcc dot gnu.org
2021-02-23 14:49 ` hp at gcc dot gnu.org
2021-02-25 23:02 ` dmalcolm at gcc dot gnu.org
2021-02-25 23:03 ` dmalcolm at gcc dot gnu.org
2021-02-26 12:58 ` rguenth at gcc dot gnu.org
2021-02-26 14:23 ` dmalcolm at gcc dot gnu.org
2021-02-26 14:33 ` dmalcolm at gcc dot gnu.org
2021-04-04 21:57 ` hp at gcc dot gnu.org
2021-04-09  8:24 ` rguenth at gcc dot gnu.org
2021-04-09 23:11 ` hp at gcc dot gnu.org [this message]
2021-04-10 17:45 ` dmalcolm at gcc dot gnu.org
2021-04-12 12:59 ` dmalcolm at gcc dot gnu.org
2021-04-13  2:23 ` hp at gcc dot gnu.org
2021-04-13  2:23 ` cvs-commit at gcc dot gnu.org
2021-04-27 11:40 ` [Bug analyzer/99212] [11/12 " jakub at gcc dot gnu.org
2021-05-04 12:32 ` rguenth at gcc dot gnu.org
2021-06-08 18:46 ` cvs-commit at gcc dot gnu.org
2021-06-08 19:30 ` [Bug analyzer/99212] [11 " dmalcolm at gcc dot gnu.org
2021-06-15  8:05 ` stefansf at linux dot ibm.com
2021-06-15 14:28 ` dmalcolm at gcc dot gnu.org
2021-06-15 21:54 ` cvs-commit at gcc dot gnu.org
2021-06-18  7:36 ` stefansf at linux dot ibm.com
2021-07-02 19:22 ` cvs-commit at gcc dot gnu.org
2021-07-02 19:22 ` cvs-commit at gcc dot gnu.org
2021-07-02 19:31 ` dmalcolm at gcc dot gnu.org

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=bug-99212-4-YVfdFyGcv3@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).