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

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

            Bug ID: 99270
           Summary: Testsuite 27_io/headers/cstdio/types_std.cc failure on
                    DragonFly
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rimvydas.jas at gmail dot com
  Target Milestone: ---

Testsuite on x86_64-*-dragonfly gives:

Running target unix
FAIL: 27_io/headers/cstdio/types_std.cc (test for excess errors)

spawn -ignore SIGHUP /build/trunk/./gcc/xg++ -shared-libgcc
-B/build/trunk/./gcc -nostdinc++
-L/build/trunk/x86_64-unknown-dragonfly5.9/libstdc++-v3/src
-L/build/trunk/x86_64-unknown-dragonfly5.9/libstdc++-v3/src/.libs
-L/build/trunk/x86_64-unknown-dragonfly5.9/libstdc++-v3/libsupc++/.libs
-B/opt/gcc11f/x86_64-unknown-dragonfly5.9/bin/
-B/opt/gcc11f/x86_64-unknown-dragonfly5.9/lib/ -isystem
/opt/gcc11f/x86_64-unknown-dragonfly5.9/include -isystem
/opt/gcc11f/x86_64-unknown-dragonfly5.9/sys-include -fchecking=1
-B/build/trunk/x86_64-unknown-dragonfly5.9/./libstdc++-v3/src/.libs
-fmessage-length=0 -fno-show-column -ffunction-sections -fdata-sections -g -O2
-DLOCALEDIR="." -nostdinc++
-I/build/trunk/x86_64-unknown-dragonfly5.9/libstdc++-v3/include/x86_64-unknown-dragonfly5.9
-I/build/trunk/x86_64-unknown-dragonfly5.9/libstdc++-v3/include
-I/data/gg/libstdc++-v3/libsupc++ -I/data/gg/libstdc++-v3/include/backward
-I/data/gg/libstdc++-v3/testsuite/util
/data/gg/libstdc++-v3/testsuite/27_io/headers/cstdio/types_std.cc
-fdiagnostics-plain-output -S -o types_std.s
/data/gg/libstdc++-v3/testsuite/27_io/headers/cstdio/types_std.cc:25: error:
aggregate 'FILE gnu::f' has incomplete type and cannot be defined
compiler exited with status 1
FAIL: 27_io/headers/cstdio/types_std.cc (test for excess errors)
Excess errors:
/data/gg/libstdc++-v3/testsuite/27_io/headers/cstdio/types_std.cc:25: error:
aggregate 'FILE gnu::f' has incomplete type and cannot be defined

extra_tool_flags are:

On DragonFly the FILE type is declared as opaque struct and its internals are
never exposed on purpose:
typedef struct __FILE FILE;

Even cppreference mentions that std::FILE may be semantically non-copyable.
Could "std::FILE f;" test be excluded by #if !defined(__DragonFly__) or simply
changed to a more usual use case of "std::FILE *fp;" ?

             reply	other threads:[~2021-02-25 14:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25 14:09 rimvydas.jas at gmail dot com [this message]
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
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@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).