public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug inline-asm/22045] can't find a register in class 'GENERAL_REGS' Date: Tue, 09 Aug 2005 17:44:00 -0000 [thread overview] Message-ID: <20050809174447.610.qmail@sourceware.org> (raw) In-Reply-To: <20050613133124.22045.macro@linux-mips.org> ------- Additional Comments From rth at gcc dot gnu dot org 2005-08-09 17:44 ------- Yes, the funny cast is *intended* to alias all memory, and thus force anything that might potentially alias the string to be written back. We don't have the ability to conclude that __d3 won't be affected. As for <bits/string.h>, the version in current glibc seems to be very different and should not exhibit the problem shown here. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22045
next prev parent reply other threads:[~2005-08-09 17:44 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-06-13 13:32 [Bug inline-asm/22045] New: " macro at linux-mips dot org 2005-06-13 13:32 ` [Bug inline-asm/22045] " macro at linux-mips dot org 2005-06-13 13:33 ` macro at linux-mips dot org 2005-06-13 13:45 ` pinskia at gcc dot gnu dot org 2005-06-13 14:14 ` macro at linux-mips dot org 2005-06-13 14:17 ` pinskia at gcc dot gnu dot org 2005-06-13 14:44 ` macro at linux-mips dot org 2005-06-14 7:06 ` vda at port dot imtp dot ilyichevsk dot odessa dot ua 2005-06-19 13:04 ` pinskia at gcc dot gnu dot org 2005-08-08 17:42 ` macro at linux-mips dot org 2005-08-08 17:43 ` macro at linux-mips dot org 2005-08-08 18:09 ` rth at gcc dot gnu dot org 2005-08-08 18:12 ` rth at gcc dot gnu dot org 2005-08-08 22:10 ` rth at gcc dot gnu dot org 2005-08-08 22:32 ` rth at gcc dot gnu dot org 2005-08-09 11:38 ` macro at linux-mips dot org 2005-08-09 17:44 ` rth at gcc dot gnu dot org [this message] 2005-08-09 18:23 ` macro at linux-mips 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=20050809174447.610.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).