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 target/110027] Misaligned vector store on detect_stack_use_after_return
Date: Mon, 29 May 2023 20:54:17 +0000	[thread overview]
Message-ID: <bug-110027-4-sTE8qQr1Yk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110027-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|                            |x86_64-linux-gnu
     Ever confirmed|0                           |1
          Component|sanitizer                   |target
   Last reconfirmed|                            |2023-05-29
             Status|UNCONFIRMED                 |NEW
           Keywords|                            |wrong-code
      Known to work|                            |7.5.0

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Samuel Neves from comment #0)
> Interestingly this seems to be only reproducible on Arch Linux. Other gcc
> 13.1.1 builds, Fedora for instance, seem to behave correctly. It is unclear
> to me what the reason for this is.

So I figured out where the difference comes from: -fstack-protector-strong .
That is Arch linux defaults to enabling -fstack-protector-strong while Fedora
does not.

apinski@xeond:~/src/upstream-gcc$ ~/upstream-gcc/bin/gcc t.c  -mavx512f
-fsanitize=address  -g
apinski@xeond:~/src/upstream-gcc$ LD_LIBRARY_PATH=~/upstream-gcc/lib64 ./a.out
;echo $?
0


apinski@xeond:~/src/upstream-gcc$ ~/upstream-gcc/bin/gcc t.c  -mavx512f
-fsanitize=address  -g  -fstack-protector-strong
apinski@xeond:~/src/upstream-gcc$ LD_LIBRARY_PATH=~/upstream-gcc/lib64 ./a.out
;echo $?
AddressSanitizer:DEADLYSIGNAL
=================================================================
==22803==ERROR: AddressSanitizer: SEGV on unknown address (pc 0x000000400929 bp
0x7fff1989a900 sp 0x7fff1989a800 T0)
==22803==The signal is caused by a READ memory access.
==22803==Hint: this fault was caused by a dereference of a high value address
(see register values below).  Disassemble the provided pc to learn which
register was used.
    #0 0x400929 in main /home/apinski/src/upstream-gcc/t.c:5
    #1 0x7ff88bf72c86 in __libc_start_main
(/lib/x86_64-linux-gnu/libc.so.6+0x21c86) (BuildId:
f7307432a8b162377e77a182b6cc2e53d771ec4b)
    #2 0x400769 in _start (/bajas/pinskia/src/upstream-gcc/a.out+0x400769)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV /home/apinski/src/upstream-gcc/t.c:5 in main
==22803==ABORTING
1

  reply	other threads:[~2023-05-29 20:54 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-29 20:18 [Bug sanitizer/110027] New: " sneves at dei dot uc.pt
2023-05-29 20:54 ` pinskia at gcc dot gnu.org [this message]
2023-05-30  8:06 ` [Bug target/110027] " rguenth at gcc dot gnu.org
2023-05-30 14:49 ` oconnor663 at gmail dot com
2023-10-22 18:06 ` gcc at sicherha dot de
2023-12-01 17:42 ` pinskia at gcc dot gnu.org
2023-12-01 17:46 ` pinskia at gcc dot gnu.org
2023-12-17 23:24 ` pinskia at gcc dot gnu.org
2024-03-08  4:13 ` pinskia at gcc dot gnu.org
2024-03-08 11:41 ` elrodc at gmail dot com
2024-03-08 18:10 ` gcc at sicherha dot de
2024-03-08 18:52 ` [Bug target/110027] [11/12/13/14 regression] " sjames at gcc dot gnu.org
2024-03-11  3:28 ` liuhongt at gcc dot gnu.org
2024-03-12  5:10 ` liuhongt at gcc dot gnu.org
2024-03-12  6:35 ` liuhongt at gcc dot gnu.org
2024-03-15  1:51 ` liuhongt at gcc dot gnu.org
2024-03-25 12:34 ` rguenth at gcc dot gnu.org
2024-04-08 15:43 ` xry111 at gcc dot gnu.org
2024-04-09 18:25 ` [Bug target/110027] [11/12/13/14 regression] Stack objects with extended alignments (vectors etc) misaligned " jakub at gcc dot gnu.org
2024-04-10 10:25 ` [Bug middle-end/110027] " jakub at gcc dot gnu.org
2024-04-11  6:53 ` liuhongt at gcc dot gnu.org
2024-04-11  8:16 ` jakub at gcc dot gnu.org
2024-04-11  9:14 ` cvs-commit at gcc dot gnu.org
2024-04-11 10:06 ` [Bug middle-end/110027] [11/12/13 " jakub at gcc dot gnu.org
2024-04-12 18:09 ` carlos.seo at linaro dot org
2024-04-21  4:09 ` cvs-commit at gcc dot gnu.org
2024-04-23  6:44 ` [Bug middle-end/110027] [11/12 " 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-110027-4-sTE8qQr1Yk@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).