public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/113194] Hangup build ExtractAPIConsumer.cpp at -Og Date: Tue, 02 Jan 2024 04:29:54 +0000 [thread overview] Message-ID: <bug-113194-4-oWO1laZF6O@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113194-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113194 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Works for me with r14-6875-g3a7dd24eadeb91 on x86_64: ./cc1plus tmp/ExtractAPIConsumer.cpp.ii -quiet -Og -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -fno-lifetime-dse -ffunction-sections -fdata-sections -fno-common -fno-strict-aliasing -fno-exceptions -funwind-tables -fno-rtti -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -Wpedantic -Wno-long-long -Wimplicit-fallthrough=3 -Wno-maybe-uninitialized -Wno-nonnull -Wno-class-memaccess -Wno-redundant-move -Wno-pessimizing-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment -Wno-misleading-indentation -Wctad-maybe-unsupported -Woverloaded-virtual=2 -std=c++17
next prev parent reply other threads:[~2024-01-02 4:29 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-02 4:06 [Bug c++/113194] New: " paul.hua.gm at gmail dot com 2024-01-02 4:08 ` [Bug c++/113194] " paul.hua.gm at gmail dot com 2024-01-02 4:29 ` pinskia at gcc dot gnu.org [this message] 2024-01-02 4:37 ` [Bug middle-end/113194] " pinskia at gcc dot gnu.org 2024-01-02 8:10 ` paul.hua.gm at gmail dot com 2024-01-02 11:48 ` [Bug debug/113194] " pinskia 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-113194-4-oWO1laZF6O@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).