public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/16815] MIPS n32/n64 inefficient code for float arguments Date: Thu, 07 Oct 2004 05:34:00 -0000 [thread overview] Message-ID: <20041007053434.4847.qmail@sourceware.org> (raw) In-Reply-To: <20040729020515.16815.wilson@gcc.gnu.org> ------- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-10-07 05:34 ------- Subject: Bug 16815 CVSROOT: /cvs/gcc Module name: gcc Changes by: rsandifo@gcc.gnu.org 2004-10-07 05:34:31 Modified files: gcc : ChangeLog function.c gcc/config/pa : pa.h Log message: PR target/16815 * function.c (assign_parm_setup_block_p): Tighten BLOCK_REG_PADDING check. * config/pa/pa.h (BLOCK_REG_PADDING): Define in terms of function_arg_padding. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&r1=2.5775&r2=2.5776 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/function.c.diff?cvsroot=gcc&r1=1.579&r2=1.580 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/config/pa/pa.h.diff?cvsroot=gcc&r1=1.235&r2=1.236 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16815
next prev parent reply other threads:[~2004-10-07 5:34 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-07-29 2:05 [Bug middle-end/16815] New: " wilson at gcc dot gnu dot org 2004-07-29 2:08 ` [Bug middle-end/16815] " pinskia at gcc dot gnu dot org 2004-07-29 2:10 ` wilson at gcc dot gnu dot org 2004-07-29 2:25 ` wilson at tuliptree dot org 2004-07-29 4:26 ` pinskia at gcc dot gnu dot org 2004-09-30 11:19 ` giovannibajo at libero dot it 2004-10-07 5:34 ` cvs-commit at gcc dot gnu dot org [this message] 2004-10-07 5:37 ` rsandifo at gcc dot gnu dot org
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=20041007053434.4847.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).