public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ferdasi at opentrash dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109852] Making of gcc13 errors out compiling libcpp/charset.cc with Wstringop-overflow Error with "-march=native -O3 "
Date: Mon, 15 May 2023 15:44:17 +0000	[thread overview]
Message-ID: <bug-109852-4-W8xZz2GX1S@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109852-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Erich <ferdasi at opentrash dot com> ---
The output of -v ->
Lesen der Spezifikationen von
/home/xxxx/software/gcc13/host-x86_64-pc-linux-gnu/prev-gcc/specs
COLLECT_GCC=/home/xxxx/software/gcc13/host-x86_64-pc-linux-gnu/prev-gcc/xg++
Ziel: x86_64-pc-linux-gnu
Konfiguriert mit: configure --disable-multilib
--prefix=/home/xxxx/software/gccinstall
Thread-Modell: posix
Unterstützte LTO-Kompressionsalgorithmen: zlib zstd
gcc-Version 14.0.0 20230514 (experimental) (GCC)

      parent reply	other threads:[~2023-05-15 15:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-14 10:01 [Bug libgcc/109852] New: Making of gcc13 stops at libcpp/charset.cc with Error ferdasi at opentrash dot com
2023-05-14 14:13 ` [Bug tree-optimization/109852] Making of gcc13 errors out compiling libcpp/charset.cc with Error with "-march=native -O3 " pinskia at gcc dot gnu.org
2023-05-14 18:53 ` [Bug tree-optimization/109852] Making of gcc13 errors out compiling libcpp/charset.cc with Wstringop-overflow " pinskia at gcc dot gnu.org
2023-05-15  6:10 ` xry111 at gcc dot gnu.org
2023-05-15 15:33 ` ferdasi at opentrash dot com
2023-05-15 15:44 ` ferdasi at opentrash dot com [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-109852-4-W8xZz2GX1S@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).