public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/37048] [4.4 Regression] Revision 138835 breaks bootstrap
Date: Thu, 07 Aug 2008 14:53:00 -0000 [thread overview]
Message-ID: <20080807145214.11233.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37048-682@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from hjl dot tools at gmail dot com 2008-08-07 14:52 -------
(In reply to comment #4)
> Subject: Re: [4.4 Regression] Revision 138835 breaks bootstrap
>
> Hi,
> thanks for testcase, for some reason it does not reproduce on our
> testing setup, probably due to ancient glibc that still has
> memcpy/memset inlines.
>
> This patch should fix it, I am testing it right now but I am not sure I
> will be able to commit before tomorro wunforutnately.
> The problem is that we now use single stringops on optimize_size
> regions, but the patterns are disabled. It is not problem to enable
> them; we never produce them directly, only via the stringop expanders.
> (at least I am convinced combine won't produce this)
>
I am testing it now. I will commit it for you if it works and no one
beats me on it. Thanks.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37048
next prev parent reply other threads:[~2008-08-07 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 13:08 [Bug target/37048] New: " hjl dot tools at gmail dot com
2008-08-07 13:22 ` [Bug target/37048] " hjl dot tools at gmail dot com
2008-08-07 13:22 ` hjl dot tools at gmail dot com
2008-08-07 13:49 ` hjl dot tools at gmail dot com
2008-08-07 14:32 ` jh at suse dot cz
2008-08-07 14:53 ` hjl dot tools at gmail dot com [this message]
2008-08-07 14:57 ` hubicka at gcc dot gnu dot org
2008-08-07 17:24 ` hjl dot tools at gmail dot com
2008-08-10 20:21 ` 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=20080807145214.11233.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: link
Be 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).