public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zhongyunde at huawei dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107316] [aarch64] Init big const value should be improved compare to llvm
Date: Sun, 23 Oct 2022 05:55:16 +0000 [thread overview]
Message-ID: <bug-107316-4-Kb79vDIvY0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107316-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107316
--- Comment #2 from vfdff <zhongyunde at huawei dot com> ---
(In reply to Andrew Pinski from comment #1)
> I suspect this is just a dup of bug 106583 and will be fixed by the patch
> which was submitted recently
> (https://gcc.gnu.org/pipermail/gcc-patches/2022-October/603905.html).
Thanks very much, I'll check that after the patch will be committed to the
upstream.
next prev parent reply other threads:[~2022-10-23 5:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 11:26 [Bug c/107316] New: " zhongyunde at huawei dot com
2022-10-19 16:15 ` [Bug target/107316] " pinskia at gcc dot gnu.org
2022-10-23 5:55 ` zhongyunde at huawei dot com [this message]
2022-10-25 12:05 ` wilco at gcc dot gnu.org
2022-10-25 12:14 ` wilco at gcc dot gnu.org
2022-11-28 22:42 ` 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-107316-4-Kb79vDIvY0@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).