public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "syq at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/112759] [13/14 regression] mips -march=native detection broken with gcc 13+ since r13-3178-g66c48be23e0fa5
Date: Mon, 18 Dec 2023 02:24:54 +0000	[thread overview]
Message-ID: <bug-112759-4-T01zq1SR2i@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112759-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from YunQiang Su <syq at gcc dot gnu.org> ---
It's my fault.
I misunderstanding `reconcat`:

if `optr` is NULL, it cannot work as the `s1` at the sametime.
If so, the return string will be empty.

So, let's define and initial ret like this:

char *ret = concat(" "); 

Any idea?

  parent reply	other threads:[~2023-12-18  2:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29  7:10 [Bug driver/112759] New: [13 regression] mips -march=native detection broken with gcc 13+ matoro_gcc_bugzilla at matoro dot tk
2023-11-29  7:10 ` [Bug driver/112759] " matoro_gcc_bugzilla at matoro dot tk
2023-11-29 22:16 ` [Bug driver/112759] [13/14 " pinskia at gcc dot gnu.org
2023-11-30  8:42 ` rguenth at gcc dot gnu.org
2023-11-30 15:37 ` matoro_gcc_bugzilla at matoro dot tk
2023-12-13  0:47 ` pinskia at gcc dot gnu.org
2023-12-18  2:24 ` syq at gcc dot gnu.org [this message]
2023-12-18  3:16 ` [Bug driver/112759] [13/14 regression] mips -march=native detection broken with gcc 13+ since r13-3178-g66c48be23e0fa5 syq at gcc dot gnu.org
2023-12-23  8:47 ` cvs-commit at gcc dot gnu.org
2023-12-23  8:51 ` cvs-commit at gcc dot gnu.org
2023-12-23  8:55 ` syq 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-112759-4-T01zq1SR2i@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).