public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "falk at debian dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/12885] gcc targetting hppa uses memcpy() with -fno-builtin Date: Mon, 03 Nov 2003 19:17:00 -0000 [thread overview] Message-ID: <20031103191723.27453.qmail@sources.redhat.com> (raw) In-Reply-To: <20031103140153.12885.phil@secdev.org> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12885 falk at debian dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID ------- Additional Comments From falk at debian dot org 2003-11-03 19:17 ------- It turns out that current policy is to emit some function calls even with -ffreestanding. See bug 4417.
prev parent reply other threads:[~2003-11-03 19:17 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-11-03 14:02 [Bug c/12885] New: " gcc-bugzilla at gcc dot gnu dot org 2003-11-03 15:42 ` [Bug c/12885] " falk at debian dot org 2003-11-03 15:49 ` pinskia at gcc dot gnu dot org 2003-11-03 17:45 ` phil at secdev dot org 2003-11-03 19:17 ` falk at debian dot org [this message]
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=20031103191723.27453.qmail@sources.redhat.com \ --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).