public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug debug/39368] New: loc_descriptor doesn't call delegitimize_address on MEMs
@ 2009-03-04 20:58 amylaar at gcc dot gnu dot org
2009-03-05 2:30 ` [Bug debug/39368] " amylaar at gcc dot gnu dot org
2010-05-26 7:03 ` jakub at gcc dot gnu dot org
0 siblings, 2 replies; 3+ messages in thread
From: amylaar at gcc dot gnu dot org @ 2009-03-04 20:58 UTC (permalink / raw)
To: gcc-bugs
For a RISC target that doesn't allow memory-indirect addressing, the
proper way to represent an access of a symbol found in the GOT is to
first load the symbol from the GOT into a register, and then use
that register for memory access or call as needed.
For proper scheduling and instruction selection, the symbol load
source should be represented as what it is, i.e. a MEM.
So we have a (MEM (unspec ... UNSPEC_GOT)) .
For the purposes of debug output, this should be translated back into
the symbol_ref it represents.
However, loc_descriptor looks only into the address inside a MEM,
it does not process the entire mem with targetm.delegitimize_address.
I.e. there is no way to get rid of the MEM if it is not nested in
another MEM.
--
Summary: loc_descriptor doesn't call delegitimize_address on MEMs
Product: gcc
Version: 4.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: amylaar at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39368
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug debug/39368] loc_descriptor doesn't call delegitimize_address on MEMs
2009-03-04 20:58 [Bug debug/39368] New: loc_descriptor doesn't call delegitimize_address on MEMs amylaar at gcc dot gnu dot org
@ 2009-03-05 2:30 ` amylaar at gcc dot gnu dot org
2010-05-26 7:03 ` jakub at gcc dot gnu dot org
1 sibling, 0 replies; 3+ messages in thread
From: amylaar at gcc dot gnu dot org @ 2009-03-05 2:30 UTC (permalink / raw)
To: gcc-bugs
------- Comment #1 from amylaar at gcc dot gnu dot org 2009-03-05 02:30 -------
patch is here:
http://gcc.gnu.org/ml/gcc-patches/2009-03/msg00267.html
--
amylaar at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
OtherBugsDependingO| |39363
nThis| |
AssignedTo|unassigned at gcc dot gnu |amylaar at gcc dot gnu dot
|dot org |org
Status|UNCONFIRMED |ASSIGNED
Ever Confirmed|0 |1
Keywords| |patch
Last reconfirmed|0000-00-00 00:00:00 |2009-03-05 02:30:29
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39368
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug debug/39368] loc_descriptor doesn't call delegitimize_address on MEMs
2009-03-04 20:58 [Bug debug/39368] New: loc_descriptor doesn't call delegitimize_address on MEMs amylaar at gcc dot gnu dot org
2009-03-05 2:30 ` [Bug debug/39368] " amylaar at gcc dot gnu dot org
@ 2010-05-26 7:03 ` jakub at gcc dot gnu dot org
1 sibling, 0 replies; 3+ messages in thread
From: jakub at gcc dot gnu dot org @ 2010-05-26 7:03 UTC (permalink / raw)
To: gcc-bugs
------- Comment #2 from jakub at gcc dot gnu dot org 2010-05-26 07:03 -------
Not sure whether this patch is still needed now that var-tracking already
delegitimizes MEMs (and their addresses) too.
That said, if you have a testcase where this is still needed, the patch looks
reasonable, so you might want to ping it.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39368
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-05-26 7:03 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-03-04 20:58 [Bug debug/39368] New: loc_descriptor doesn't call delegitimize_address on MEMs amylaar at gcc dot gnu dot org
2009-03-05 2:30 ` [Bug debug/39368] " amylaar at gcc dot gnu dot org
2010-05-26 7:03 ` jakub at gcc dot gnu dot org
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).