public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/106008] [12 Regression] warning: ‘(((char *)loadcmds.113_68 + _933 + 16))[329406144173384849].mapend’ may be used uninitialized [-Wmaybe-uninitialized]
Date: Thu, 16 Jun 2022 22:27:05 +0000	[thread overview]
Message-ID: <bug-106008-4-LDVSCFapdX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106008-4@http.gcc.gnu.org/bugzilla/>

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2022-06-16

--- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> ---
Simply change the cost of integer store makes the warnings to go away:

diff --git a/gcc/config/i386/x86-tune-costs.h
b/gcc/config/i386/x86-tune-costs.h
index 6c9066c84cc..b83bb79c065 100644
--- a/gcc/config/i386/x86-tune-costs.h
+++ b/gcc/config/i386/x86-tune-costs.h
@@ -3276,7 +3276,11 @@ struct processor_costs generic_cost = {
   {6, 6, 6},           /* cost of loading integer registers
                  in QImode, HImode and SImode.
                  Relative to reg-reg move (2).  */
+#if 0
   {6, 6, 6},           /* cost of storing integer registers */
+#else
+  {8, 8, 8},           /* cost of storing integer registers */
+#endif
   {6, 6, 6, 10, 15},         /* cost of loading SSE register
                  in 32bit, 64bit, 128bit, 256bit and 512bit */
   {6, 6, 6, 10, 15},         /* cost of storing SSE register

  reply	other threads:[~2022-06-16 22:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16 19:16 [Bug middle-end/106008] New: " hjl.tools at gmail dot com
2022-06-16 22:27 ` hjl.tools at gmail dot com [this message]
2022-06-17  2:55 ` [Bug middle-end/106008] [11/12 " hjl.tools at gmail dot com
2022-06-20 10:01 ` [Bug middle-end/106008] [11/12/13 " rguenth at gcc dot gnu.org
2022-06-20 10:01 ` rguenth at gcc dot gnu.org
2023-03-29 13:35 ` rguenth at gcc dot gnu.org
2023-05-29 10:07 ` [Bug middle-end/106008] [11/12/13/14 " jakub 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-106008-4-LDVSCFapdX@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).