public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/9475: Wrong ffs results Date: Tue, 28 Jan 2003 13:16:00 -0000 [thread overview] Message-ID: <20030128131600.20495.qmail@sources.redhat.com> (raw) The following reply was made to PR c/9475; it has been noted by GNATS. From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de> To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org Cc: Subject: Re: c/9475: Wrong ffs results Date: 28 Jan 2003 14:13:37 +0100 Hi, gcc thinks ffs gets its parameters on the stack: int f(unsigned dummy, unsigned x) { return __builtin_ffs(x); } f: .frame $30,32,$26,0 .mask 0x4000000,-16 ldah $29,0($27) !gpdisp!6 lda $29,0($29) !gpdisp!6 $f..ng: lda $30,-32($30) ldq $27,ffs($29) !literal!7 stq $26,16($30) .prologue 1 --> stl $17,0($30) jsr $26,($27),ffs !lituse_jsr!7 ldah $29,0($26) !gpdisp!8 addl $31,$0,$0 bis $31,$31,$31 lda $29,0($29) !gpdisp!8 ldq $26,16($30) lda $30,32($30) ret $31,($26),1 But ffs follows normal C calling conventions (first argument in $16). Any ideas which recent change might have caused this? -- Falk
next reply other threads:[~2003-01-28 13:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-28 13:16 Falk Hueffner [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-29 0:13 bangerth 2003-01-29 0:06 Falk Hueffner 2003-01-28 12:56 Falk Hueffner
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=20030128131600.20495.qmail@sources.redhat.com \ --to=falk.hueffner@student.uni-tuebingen.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).