public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/96347] note: non-delegitimized UNSPEC UNSPEC_TP (19) found in variable location
Date: Wed, 29 Jul 2020 18:12:34 +0000 [thread overview]
Message-ID: <bug-96347-4-C2611OoVMp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96347-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96347
Iain Buclaw <ibuclaw at gdcproject dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #48946|0 |1
is obsolete| |
--- Comment #4 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
Created attachment 48953
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48953&action=edit
delegitimize mem(plus (unspec reg) tls)
Second patch, this time dealing with the following insn
---
(mem/f/c:DI (plus:DI (unspec:DI [
(const_int 0 [0])
] UNSPEC_TP)
(reg:DI 89)) [1 MEM <int *> [(struct Darray *)&testYearsBC + 8B]+0 S8
A64])
---
After ix86_delegitimize_tls_address, it becomes
---
(mem/f/c:DI (reg/f:DI 6 bp [90]) [1 MEM <int *> [(struct Darray *)&testYearsBC
+ 8B]+0 S8 A64])
---
Doesn't change assembly produced for given test, but alters debug output:
---
@@ -1105,12 +1105,9 @@ testYearsBC:
.LLST4:
.quad .LVL7
.quad .LVL8-1
- .value 0xd
- .byte 0xe
- .long testYearsBC@dtpoff, 0
- .byte 0xe0
- .byte 0x23
- .uleb128 0x8
+ .value 0x3
+ .byte 0x76
+ .sleb128 0
.byte 0x6
.quad 0
.quad 0
@@ -1148,15 +1145,12 @@ testYearsBC:
.LLST6:
.quad .LVL9
.quad .LVL9
- .value 0x11
+ .value 0x7
.byte 0x50
.byte 0x93
.uleb128 0x8
- .byte 0xe
- .long testYearsBC@dtpoff, 0
- .byte 0xe0
- .byte 0x23
- .uleb128 0x8
+ .byte 0x76
+ .sleb128 0
.byte 0x93
.uleb128 0x8
.quad 0
@@ -1167,15 +1161,12 @@ testYearsBC:
.LLST7:
.quad .LVL9
.quad .LVL9
- .value 0x11
+ .value 0x7
.byte 0x50
.byte 0x93
.uleb128 0x8
- .byte 0xe
- .long testYearsBC@dtpoff, 0
- .byte 0xe0
- .byte 0x23
- .uleb128 0x8
+ .byte 0x76
+ .sleb128 0
.byte 0x93
.uleb128 0x8
.quad 0
---
next prev parent reply other threads:[~2020-07-29 18:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 22:19 [Bug target/96347] New: " ibuclaw at gdcproject dot org
2020-07-27 22:22 ` [Bug target/96347] " ibuclaw at gdcproject dot org
2020-07-28 13:06 ` ibuclaw at gdcproject dot org
2020-07-28 14:55 ` ibuclaw at gdcproject dot org
2020-07-29 18:12 ` ibuclaw at gdcproject dot org [this message]
2020-08-06 12:02 ` ibuclaw at gdcproject dot org
2023-10-18 18:59 ` ibuclaw at gdcproject dot 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-96347-4-C2611OoVMp@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).