https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61300
Alan Modra changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61300
--- Comment #10 from Alan Modra ---
Author: amodra
Date: Wed Jun 11 23:50:16 2014
New Revision: 211483
URL: http://gcc.gnu.org/viewcvs?rev=211483&root=gcc&view=rev
Log:
PR target/61300
* doc/tm.texi.in (INCOMING_REG_PARM_STACK_SPACE): Do
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61300
--- Comment #9 from Alan Modra ---
Author: amodra
Date: Wed Jun 11 23:49:49 2014
New Revision: 211482
URL: http://gcc.gnu.org/viewcvs?rev=211482&root=gcc&view=rev
Log:
PR target/61300
* doc/tm.texi.in (INCOMING_REG_PARM_STACK_SPACE): Doc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61300
--- Comment #8 from Alan Modra ---
Author: amodra
Date: Fri Jun 6 01:04:22 2014
New Revision: 211296
URL: http://gcc.gnu.org/viewcvs?rev=211296&root=gcc&view=rev
Log:
PR target/61300
* doc/tm.texi.in (INCOMING_REG_PARM_STACK_SPACE): Doc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61300
--- Comment #7 from Alan Modra ---
No, I don't believe there is a convenient way we can look at the
REG_PARM_STACK_SPACE argument to determine whether it was used for a call or
for a function body. (I did think it might be possible, hence my com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61300
Ulrich Weigand changed:
What|Removed |Added
CC||uweigand at gcc dot gnu.org
--- Comment
