public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/104407] [10/11/12 Regression] '-fcompare-debug' failure (length) w/ -std=c++17 -O1
Date: Sun, 06 Feb 2022 08:51:17 +0000	[thread overview]
Message-ID: <bug-104407-4-t3nqPY9gWY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104407-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |10.4
           Keywords|                            |needs-bisection
   Last reconfirmed|                            |2022-02-06
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1
      Known to fail|                            |10.3.0, 11.1.0
      Known to work|                            |10.2.0

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed, the alignment with -g is 64 for the load but 128 without -g.

-g:
(insn 9 8 10 (set (reg/f:DI 83)
        (symbol_ref:DI ("a") [flags 0x2]  <var_decl 0x7f642e3a7cf0 a>))
"/app/example.cpp":4:6 -1
     (nil))

(insn 10 9 11 (set (reg:TI 84)
        (mem/c:TI (reg/f:DI 83) [1 a+0 S16 A64])) "/app/example.cpp":4:6 -1
     (nil))

vs:
(insn 6 5 7 (set (reg/f:DI 83)
        (symbol_ref:DI ("a") [flags 0x2]  <var_decl 0x7f69102a2cf0 a>))
"/app/example.cpp":4:6 -1
     (nil))

(insn 7 6 8 (set (reg:TI 84)
        (mem/c:TI (reg/f:DI 83) [1 a+0 S16 A128])) "/app/example.cpp":4:6 -1
     (nil))


The alignment in the assembly is 16 (128) for both:
        .align 16
        .type   a, @object
        .size   a, 24
a:
        .zero   24

It not obvious what is causing the issue though.

Here is a C++98 testcase that does not depend on C++17 features.

  reply	other threads:[~2022-02-06  8:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-06  7:32 [Bug debug/104407] New: " asolokha at gmx dot com
2022-02-06  8:51 ` pinskia at gcc dot gnu.org [this message]
2022-02-06  8:52 ` [Bug target/104407] " pinskia at gcc dot gnu.org
2022-02-07  9:05 ` jakub at gcc dot gnu.org
2022-02-07  9:17 ` jakub at gcc dot gnu.org
2022-02-07  9:19 ` jakub at gcc dot gnu.org
2022-02-07  9:23 ` jakub at gcc dot gnu.org
2022-02-07  9:31 ` rguenth at gcc dot gnu.org
2022-02-07  9:38 ` jakub at gcc dot gnu.org
2022-02-07  9:42 ` jakub at gcc dot gnu.org
2022-02-07  9:42 ` rguenth at gcc dot gnu.org
2022-02-07  9:44 ` rguenth at gcc dot gnu.org
2022-02-07  9:50 ` [Bug debug/104407] " jakub at gcc dot gnu.org
2022-02-07 10:50 ` rguenth at gcc dot gnu.org
2022-02-07 11:10 ` jakub at gcc dot gnu.org
2022-02-07 11:22 ` rguenther at suse dot de
2022-02-07 11:35 ` jakub at gcc dot gnu.org
2022-02-09 14:19 ` cvs-commit at gcc dot gnu.org
2022-02-09 14:19 ` [Bug debug/104407] [10/11 " jakub at gcc dot gnu.org
2022-06-28 10:48 ` jakub at gcc dot gnu.org
2023-07-07 10:42 ` [Bug debug/104407] [11 " rguenth 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-104407-4-t3nqPY9gWY@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).