http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53249
--- Comment #13 from hjl at gcc dot gnu.org 2012-05-09
13:32:22 UTC ---
Author: hjl
Date: Wed May 9 13:32:13 2012
New Revision: 187331
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=187331
Log:
Add a test for PR middle-end/53249
PR
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53249
rsand...@gcc.gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53249
--- Comment #11 from rsandifo at gcc dot gnu.org
2012-05-09 09:23:03 UTC ---
Author: rsandifo
Date: Wed May 9 09:22:57 2012
New Revision: 187320
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=187320
Log:
gcc/
PR middle-end/53249
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53249
--- Comment #10 from H.J. Lu 2012-05-06 16:00:35
UTC ---
(In reply to comment #9)
> "hjl.tools at gmail dot com" writes:
> > get_address_mode in dwarf2out.c works for this testcase.
>
> Yeah, that's what I was testing FWIW. If x32 wants to do
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53249
--- Comment #9 from rdsandiford at googlemail dot com 2012-05-06 15:56:09 UTC ---
"hjl.tools at gmail dot com" writes:
> get_address_mode in dwarf2out.c works for this testcase.
Yeah, that's what I was testing FWIW. If x32 wants to do this,
the
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53249
H.J. Lu changed:
What|Removed |Added
Status|ASSIGNED|UNCONFIRMED
Ever Confirmed|1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53249
rsand...@gcc.gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53249
--- Comment #6 from H.J. Lu 2012-05-06 14:54:10
UTC ---
Can you just use GET_MODE (mem) instead of
targetm.addr_space.address_mode (MEM_ADDR_SPACE (mem))
when you change plus_constant (mem, offset)?
At least, you should allow a backend to do
plu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53249
--- Comment #5 from H.J. Lu 2012-05-06 14:35:26
UTC ---
X32 is a 32bit environment for x86-64:
https://sites.google.com/site/x32abi/
Since there is no x32 mode in hardware, x32 binaries
run in pure 64-bit mode.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53249
--- Comment #4 from H.J. Lu 2012-05-06 14:28:55
UTC ---
A small testcase:
[hjl@gnu-6 pr53249]$ cat x.i
struct gomp_task
{
struct gomp_task *parent;
};
struct gomp_thread
{
int foo1;
struct gomp_task *task;
};
extern __thread struct gomp_
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53249
H.J. Lu changed:
What|Removed |Added
CC||ubizjak at gmail dot com
Target Milestone|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53249
--- Comment #2 from rsandifo at gcc dot gnu.org
2012-05-06 10:55:48 UTC ---
Gah. Sorry for the breakage.
This is caused by the x86_64 TLS code generating a DImode
MEM address when Pmode == SImode. As you say here:
http://gcc.gnu.org/ml/gcc-
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53249
--- Comment #1 from H.J. Lu 2012-05-05 22:22:27
UTC ---
Created attachment 27322
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27322
A testcase
On Linux/x86-64:
[hjl@gnu-35 gcc]$ ./xgcc -B./ -O2 -mx32 -fPIC -S -ftls-model=initial-exec
/tm
13 matches
Mail list logo
