From: Mathieu Malaterre <malat@debian.org>
To: gcc-help <gcc-help@gcc.gnu.org>
Subject: gcc-11: -fvisibility=hidden produces a segfault
Date: Thu, 9 Dec 2021 12:21:59 +0100 [thread overview]
Message-ID: <CA+7wUsy=0cP1NKcYvNFWBJSQpUtq5rY2E+UYMg7wiOCtCtmkAg@mail.gmail.com> (raw)
Dear all,
I did read:
* https://gcc.gnu.org/bugs/minimize.html
However I am finding it very hard to reduce a test case. Basically
compiling a large c++ codebase with -fvisibility=hidden triggers a
segfault. The same c++ code does run properly when compiled with the
exact same flag under gcc (Debian 10.2.1-6) 10.2.1 20210110.
I've setup a quick c-vise script on a Debian porterbox and it has been
running for now ~2hours. Current status is (*).
Questions:
1. How long (approx) a c-vise process is supposed to be?
2. Since I've identified the culprit gcc flag, isn't there a better
(pragmatic) approach to reducing the test case ?
Thanks much in advance
-M
(*)
% cvise --clang-delta-std "c++14" -n 1 /home/malat/reduce-ice.sh
RenderModules.cc
00:00:00 INFO ===< 15741 >===
00:00:00 INFO running 1 interestingness test in parallel
00:00:00 INFO INITIAL PASSES
00:00:00 INFO ===< IncludesPass >===
00:00:00 INFO (0.1%, 52689 bytes, 1322 lines)
00:00:57 INFO ===< UnIfDefPass >===
00:00:57 INFO ===< CommentsPass >===
00:01:06 INFO ===< IfPass >===
00:01:06 INFO ===< LineMarkersPass >===
00:01:06 INFO ===< BlankPass >===
00:01:14 INFO ===< ClangBinarySearchPass::replace-function-def-with-decl >===
00:07:57 INFO ===< ClangBinarySearchPass::remove-unused-function >===
00:14:48 INFO ===< LinesPass::0 >===
next reply other threads:[~2021-12-09 11:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 11:21 Mathieu Malaterre [this message]
2021-12-09 11:34 ` Jonathan Wakely
2021-12-09 13:27 ` Mathieu Malaterre
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='CA+7wUsy=0cP1NKcYvNFWBJSQpUtq5rY2E+UYMg7wiOCtCtmkAg@mail.gmail.com' \
--to=malat@debian.org \
--cc=gcc-help@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).