[Bug target/14907] bogus sign/zero extension when relaying parameters with regparm

2024-10-28 Thread hjl.tools at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=14907 --- Comment #7 from H.J. Lu --- Created attachment 59467 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59467&action=edit A patch I am testing this.

[Bug target/14907] bogus sign/zero extension when relaying parameters with regparm

2024-10-27 Thread hjl.tools at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=14907 --- Comment #6 from H.J. Lu --- *** Bug 117310 has been marked as a duplicate of this bug. ***

[Bug target/14907] bogus sign/zero extension when relaying parameters with regparm

2024-10-26 Thread hjl.tools at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=14907 --- Comment #5 from H.J. Lu --- (In reply to Nicholas Miell from comment #4) > This also occurs on AMD64 without any special attributes (the ABI passes > params in registers already). > > When compiling: > extern char c2(char); > char c1(char c)

[Bug target/14907] bogus sign/zero extension when relaying parameters with regparm

2006-02-28 Thread nmiell at comcast dot net
--- Comment #4 from nmiell at comcast dot net 2006-03-01 05:54 --- This also occurs on AMD64 without any special attributes (the ABI passes params in registers already). When compiling: extern char c2(char); char c1(char c) { return c2(c); } with gcc -Wall -O2 -S tail-char.c using gcc