public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/99270] Testsuite 27_io/headers/cstdio/types_std.cc failure on DragonFly
Date: Thu, 25 Feb 2021 15:01:10 +0000	[thread overview]
Message-ID: <bug-99270-4-ZQXezLGbmQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99270-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Interestingly, in C99 we have:

  Types are partitioned into object types (types that fully describe objects),
  function types (types that describe functions), and incomplete types (types
  that describe objects but lack information needed to determine their sizes).

And FILE is specified to be an object type, which means it can't be incomplete.

http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1439.pdf changed that text for
C11 so that incomplete types are a sub-category of object type, and
intentionally didn't change the definition of FILE, allowing it to be
incomplete (see last page of N1439).

Not that it matters, we should fix the test either way. Just a curiosity.

  parent reply	other threads:[~2021-02-25 15:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25 14:09 [Bug libstdc++/99270] New: " rimvydas.jas at gmail dot com
2021-02-25 14:38 ` [Bug libstdc++/99270] " redi at gcc dot gnu.org
2021-02-25 15:01 ` redi at gcc dot gnu.org [this message]
2021-02-25 15:36 ` cvs-commit at gcc dot gnu.org
2021-02-25 15:36 ` redi 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-99270-4-ZQXezLGbmQ@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).