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 target/19558] openssl speed compiled with 20051020 gcc-4.0 (HEAD) segfaults Date: Sun, 23 Jan 2005 22:05:00 -0000 [thread overview] Message-ID: <20050123220455.30193.qmail@sourceware.org> (raw) In-Reply-To: <20050121021840.19558.gj@pointblue.com.pl> ------- Additional Comments From rth at gcc dot gnu dot org 2005-01-23 22:04 ------- No, it should not. See the AMD K8 documentation for recommended nop sequences. -- What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution| |INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19558
next prev parent reply other threads:[~2005-01-23 22:05 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-01-21 2:18 [Bug c/19558] New: " gj at pointblue dot com dot pl 2005-01-21 2:22 ` [Bug target/19558] " pinskia at gcc dot gnu dot org 2005-01-21 2:49 ` gj at pointblue dot com dot pl 2005-01-21 9:10 ` steven at gcc dot gnu dot org 2005-01-21 9:13 ` steven at gcc dot gnu dot org 2005-01-21 9:43 ` gj at pointblue dot com dot pl 2005-01-21 10:08 ` gj at pointblue dot com dot pl 2005-01-21 12:11 ` gj at pointblue dot com dot pl 2005-01-23 22:05 ` rth at gcc dot gnu dot org [this message] 2005-01-24 1:50 ` gj at pointblue dot com dot pl 2005-01-24 18:48 ` gj at pointblue dot com dot pl 2005-01-24 19:01 ` pinskia at gcc dot gnu dot org 2005-01-24 20:37 ` gj at pointblue dot com dot pl 2005-01-27 6:24 ` rth at gcc dot gnu dot org 2005-01-27 13:46 ` gj at pointblue dot com dot pl 2005-05-31 3:47 ` dank at kegel dot com 2005-05-31 4:17 ` pinskia 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=20050123220455.30193.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).