public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/99896] New: g++ drops -lc Date: Sat, 03 Apr 2021 13:04:49 +0000 [thread overview] Message-ID: <bug-99896-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99896 Bug ID: 99896 Summary: g++ drops -lc Product: gcc Version: 10.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: driver Assignee: unassigned at gcc dot gnu.org Reporter: vries at gcc dot gnu.org Target Milestone: --- [ Spinoff from gdb PR https://sourceware.org/bugzilla/show_bug.cgi?id=27681 . ] Consider the following test-case, consisting of: ... $ cat main.c #include <assert.h> #include <stddef.h> #ifndef _GNU_SOURCE #define _GNU_SOURCE #endif #include <regex.h> extern void foo (void); int main (void) { regex_t re; int res = regcomp (&re, "bla", 0); assert (res == 0); int res2 = regexec (&re, "bla", 0, NULL, 0); assert (res2 == 0); regoff_t res3 = re_search (&re, "bla", 3, 0, 3, NULL); assert (res3 == 0); foo (); return 0; } ... and: ... $ cat foo.c #include <assert.h> #include <stddef.h> #include <pcre2posix.h> extern void foo (void); void foo (void) { regex_t re; int res = pcre2_regcomp (&re, "bla", 0); assert (res == 0); int res2 = pcre2_regexec (&re, "bla", 0, NULL, 0); assert (res2 == 0); } ... We can compile with gcc and run like this: ... $ gcc main.c -lc foo.c -lpcre2-posix $ ./a.out $ ... likewise, with clang: ... $ clang main.c -lc foo.c -lpcre2-posix $ ./a.out $ ... likewise, with clang++: ... $ clang++ -x c++ main.c -lc foo.c -lpcre2-posix $ ./a.out $ ... but with g++: ... $ g++ -x c++ main.c -lc foo.c -lpcre2-posix $ ./a.out Segmentation fault (core dumped) $ ... Using -v, we can see what goes wrong. With gcc, we have: ... collect2 ... main.o -lc foo.o -lpcre2-posix ... ... With g++, we have instead: ... collect2 ... main.o foo.o -lpcre2-posix ... ... Workaround: use -Wl: ... $ g++ -x c++ main.c -Wl,-lc foo.c -lpcre2-posix $ ./a.out $ ...
next reply other threads:[~2021-04-03 13:04 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-03 13:04 vries at gcc dot gnu.org [this message] 2021-04-03 14:32 ` [Bug driver/99896] " redi at gcc dot gnu.org 2021-04-03 16:57 ` vries at gcc dot gnu.org 2021-04-03 18:01 ` schwab@linux-m68k.org 2021-04-03 20:30 ` redi at gcc dot gnu.org 2021-04-03 22:45 ` schwab@linux-m68k.org 2021-04-04 2:02 ` vries at gcc dot gnu.org 2021-04-06 14:16 ` matz 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-99896-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: linkBe 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).