public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "xanclic at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/56888] memcpy implementation optimized as a call to memcpy Date: Tue, 09 Apr 2013 13:20:00 -0000 [thread overview] Message-ID: <bug-56888-4-RT3cXYZPFH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56888-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888 --- Comment #7 from Max Reitz <xanclic at gmail dot com> 2013-04-09 13:20:06 UTC --- (In reply to comment #6) > On Tue, 9 Apr 2013, xanclic at gmail dot com wrote: > > > > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888 > > > > --- Comment #5 from Max Reitz <xanclic at gmail dot com> 2013-04-09 13:02:19 UTC --- > > (In reply to comment #3) > > > Just add -fno-tree-loop-distribute-patterns to the already long list of options > > > you need for compilation of certain routines in your C library. > > > > This works for me, however, I don't see this parameter documented in gcc's > > manpage (which might prove helpful). > > It is documented in it's "positive" form, -ftree-loop-distribute-patterns Oh, now that's embarrassing… Sorry :-/ Well then, this seems to be exactly the thing I've been looking for. Thanks! >From gcc-bugs-return-419600-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Apr 09 13:29:58 2013 Return-Path: <gcc-bugs-return-419600-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 5845 invoked by alias); 9 Apr 2013 13:29:58 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 5791 invoked by uid 48); 9 Apr 2013 13:29:55 -0000 From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/56883] error openmp parallel for order Date: Tue, 09 Apr 2013 13:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Keywords: X-Bugzilla-Severity: major X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Known to work Known to fail Message-ID: <bug-56883-4-uyecnruWsW@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-56883-4@http.gcc.gnu.org/bugzilla/> References: <bug-56883-4@http.gcc.gnu.org/bugzilla/> X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 X-SW-Source: 2013-04/txt/msg00745.txt.bz2 Content-length: 1016 http://gcc.gnu.org/bugzilla/show_bug.cgi?idV883 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |4.9.0 Known to fail|4.9.0 | --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-04-09 13:29:54 UTC --- Author: jakub Date: Tue Apr 9 13:25:58 2013 New Revision: 197633 URL: http://gcc.gnu.org/viewcvs?rev\x197633&root=gcc&view=rev Log: PR middle-end/56883 * omp-low.c (expand_omp_for_generic, expand_omp_for_static_nochunk, expand_omp_for_static_chunk): Use simple_p = true in force_gimple_operand_gsi calls when assigning to addressable decls. * c-c++-common/gomp/pr56883.c: New test. Added: trunk/gcc/testsuite/c-c++-common/gomp/pr56883.c Modified: trunk/gcc/ChangeLog trunk/gcc/omp-low.c trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2013-04-09 13:20 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-08 23:40 [Bug middle-end/56888] New: " xanclic at gmail dot com 2013-04-09 9:59 ` [Bug middle-end/56888] " mikpe at it dot uu.se 2013-04-09 10:01 ` jakub at gcc dot gnu.org 2013-04-09 10:01 ` rguenth at gcc dot gnu.org 2013-04-09 13:02 ` xanclic at gmail dot com 2013-04-09 13:17 ` rguenther at suse dot de 2013-04-09 13:20 ` xanclic at gmail dot com [this message] 2013-04-11 11:29 ` rguenth at gcc dot gnu.org 2013-06-23 0:01 ` jeff@deseret-tech.com 2013-07-17 7:52 ` paulo@matos-sorge.com 2013-07-17 17:10 ` brooks at gcc dot gnu.org 2013-07-17 17:28 ` xanclic at gmail dot com 2013-07-17 20:36 ` schwab@linux-m68k.org 2013-07-17 20:59 ` xanclic at gmail dot com 2013-07-17 22:31 ` schwab@linux-m68k.org 2013-07-18 0:26 ` xanclic at gmail dot com 2013-07-18 10:35 ` paulo@matos-sorge.com 2013-07-28 3:30 ` bugdal at aerifal dot cx 2013-10-02 7:59 ` bernd.edlinger at hotmail dot de 2013-10-02 8:17 ` rguenth at gcc dot gnu.org 2013-10-02 8:49 ` bernd.edlinger at hotmail dot de 2013-10-02 8:59 ` rguenther at suse dot de 2014-02-17 3:48 ` janosch.rux at web dot de 2014-04-29 13:50 ` rguenth at gcc dot gnu.org 2014-04-29 13:57 ` rguenth at gcc dot gnu.org 2014-04-29 14:47 ` bugdal at aerifal dot cx 2014-05-06 10:51 ` rguenth at gcc dot gnu.org 2014-05-06 10:52 ` rguenth at gcc dot gnu.org 2014-06-06 10:40 ` terra at gnome dot org 2014-06-06 11:54 ` rguenther at suse dot de 2014-11-03 7:09 ` fd935653 at opayq dot com 2020-08-16 22:51 ` pinskia at gcc dot gnu.org 2022-06-03 6:55 ` pinskia at gcc dot gnu.org 2022-10-26 17:06 ` pinskia at gcc dot gnu.org 2023-12-18 20:59 ` terra at gnome dot org 2023-12-18 21:32 ` david at westcontrol dot com 2023-12-19 2:07 ` terra at gnome dot org 2023-12-19 8:03 ` rguenth at gcc dot gnu.org 2023-12-19 8:06 ` rguenth at gcc dot gnu.org 2023-12-19 8:28 ` david at westcontrol 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-56888-4-RT3cXYZPFH@http.gcc.gnu.org/bugzilla/ \ --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).