public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sam at gentoo dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/105709] FORTIFY_SOURCE=3 (*** buffer overflow detected ***: terminated) on Qt
Date: Tue, 24 May 2022 00:45:07 +0000	[thread overview]
Message-ID: <bug-105709-4-INhXeSqKON@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105709-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Sam James <sam at gentoo dot org> ---
Let me try hack something to reduce but test with Clang where possible. It's
hard because the mkspecs stuff which leaks into the preprocessed original
source doesn't build with Clang.

In the meantime, could you tell me if non-reduced-qt.cxx and
non-reduced-qt.ii.xz work for you?

  parent reply	other threads:[~2022-05-24  0:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24  0:07 [Bug c++/105709] New: " sam at gentoo dot org
2022-05-24  0:09 ` [Bug c++/105709] " sam at gentoo dot org
2022-05-24  0:09 ` [Bug middle-end/105709] " sam at gentoo dot org
2022-05-24  0:13 ` sam at gentoo dot org
2022-05-24  0:14 ` sam at gentoo dot org
2022-05-24  0:14 ` sam at gentoo dot org
2022-05-24  0:20 ` pinskia at gcc dot gnu.org
2022-05-24  0:28 ` pinskia at gcc dot gnu.org
2022-05-24  0:45 ` sam at gentoo dot org [this message]
2022-05-24  1:53 ` siddhesh at gcc dot gnu.org
2022-05-24  2:40 ` sam at gentoo dot org
2022-05-24  2:46 ` 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-105709-4-INhXeSqKON@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).