public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "philippe.gislard at morpho dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/15605] gcc-4.8 + tree-loop-distribute-patterns breaks is unsafe for GLIBC
Date: Wed, 25 Feb 2015 19:01:00 -0000	[thread overview]
Message-ID: <bug-15605-131-KuxhluWLVY@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15605-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=15605

--- Comment #9 from philippe.gislard at morpho dot com ---
(In reply to philippe.gislard from comment #8)
> Hi,
> 
> I'm using gcc 4.9.1, and I have and issue when reimplementing memset that is
> quite similar:
> loop inside memset is transformed into recursive call to memset
> 
> I noticed that when compiling with -fno-tree-loop-distribute-patterns has no
> impact but with -fno-tree-ch the issue disappear.
> Can someone tell me if it is related to this bug and if possible, what's
> happening exactly and if there is a better way to handle this ?
> 
> Thanks.

My bad: -fno-tree-loop-distribute-patterns DOES workaround this issue

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-02-25 19:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-11 20:01 [Bug libc/15605] New: " azanella at linux dot vnet.ibm.com
2013-06-12 17:12 ` [Bug libc/15605] " azanella at linux dot vnet.ibm.com
2013-10-10  6:06 ` tschwinge at sourceware dot org
2013-10-10 11:36 ` joseph at codesourcery dot com
2013-10-10 12:08 ` tschwinge at sourceware dot org
2013-10-23 22:39 ` roland at gnu dot org
2014-01-20 19:11 ` cvs-commit at gcc dot gnu.org
2014-01-20 19:15 ` cvs-commit at gcc dot gnu.org
2014-06-13 15:09 ` fweimer at redhat dot com
2015-02-25 18:51 ` philippe.gislard at morpho dot com
2015-02-25 19:01 ` philippe.gislard at morpho dot com [this message]
2015-08-27 22:15 ` [Bug build/15605] " jsm28 at gcc dot gnu.org
2022-04-08 21:27 ` [Bug hurd/15605] " rnewman at parasoft dot com

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=bug-15605-131-KuxhluWLVY@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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).