public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gcc-bugs at opsec dot eu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94493] FreeBSD-ports lang/gcc9 (9.3.0) on FreeBSD 13 crash if building ftp/filezilla Date: Mon, 06 Apr 2020 18:27:16 +0000 [thread overview] Message-ID: <bug-94493-4-HIzgeKuZAZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94493-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94493 --- Comment #10 from Kurt Jaeger <gcc-bugs at opsec dot eu> --- If the option -fstack-protector-strong is used, the *.i* files are empty.
prev parent reply other threads:[~2020-04-06 18:27 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-05 20:34 [Bug c++/94493] New: " gcc-bugs at opsec dot eu 2020-04-05 20:35 ` [Bug c++/94493] " gcc-bugs at opsec dot eu 2020-04-05 20:37 ` gcc-bugs at opsec dot eu 2020-04-05 20:40 ` gcc-bugs at opsec dot eu 2020-04-05 20:42 ` gcc-bugs at opsec dot eu 2020-04-06 6:47 ` marxin at gcc dot gnu.org 2020-04-06 7:29 ` rguenth at gcc dot gnu.org 2020-04-06 16:46 ` gcc-bugs at opsec dot eu 2020-04-06 16:48 ` gcc-bugs at opsec dot eu 2020-04-06 18:22 ` gerald at pfeifer dot com 2020-04-06 18:27 ` gcc-bugs at opsec dot eu [this message]
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-94493-4-HIzgeKuZAZ@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).