public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amodra at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65456] powerpc64le autovectorized copy loop missed optimization
Date: Sat, 28 Mar 2015 11:40:00 -0000	[thread overview]
Message-ID: <bug-65456-4-74hFQPFXy2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65456-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65456

Alan Modra <amodra at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |amodra at gmail dot com

--- Comment #14 from Alan Modra <amodra at gmail dot com> ---
This part
   || (((MODE) == SFmode || (MODE) == DFmode || (MODE) == TFmode        \
        || (MODE) == SDmode || (MODE) == DDmode || (MODE) == TDmode)    \
       && (ALIGN) < 32)                                                 \
is wrong for power8 too.  See "POWER8 Processor User’s Manual for the
Single-Chip Module", section 2.1.4 Storage Access Alignment Support Overview. 
According to that, alignment interrupt does not occur on misaligned floating
point loads and stores, except for the quadword insns.  Which seems to
contradict "Power ISA Version 2.07", section 6.5.8 Alignment Interrupt.  I
guess the ISA doc needs another update.
>From gcc-bugs-return-482125-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Mar 28 04:17:49 2015
Return-Path: <gcc-bugs-return-482125-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44393 invoked by alias); 28 Mar 2015 04:17:48 -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 44353 invoked by uid 55); 28 Mar 2015 04:17:45 -0000
From: "timshen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/65420] Enumerators in std::regex_constants should be constexpr variables instead
Date: Sat, 28 Mar 2015 11:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: timshen at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-65420-4-Tk3xcJjcih@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65420-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65420-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-03/txt/msg03269.txt.bz2
Content-length: 581

https://gcc.gnu.org/bugzilla/show_bug.cgi?ide420

--- Comment #1 from Tim Shen <timshen at gcc dot gnu.org> ---
Author: timshen
Date: Sat Mar 28 04:17:12 2015
New Revision: 221750

URL: https://gcc.gnu.org/viewcvs?rev"1750&root=gcc&view=rev
Log:
    PR libstdc++/65420
    * include/bits/regex_constants.h: Use constexpr variables for flags.
    * testsuite/28_regex/constants/constexpr.cc: New testcase.


Added:
    trunk/libstdc++-v3/testsuite/28_regex/constants/constexpr.cc
Modified:
    trunk/libstdc++-v3/ChangeLog
    trunk/libstdc++-v3/include/bits/regex_constants.h


  parent reply	other threads:[~2015-03-28  2:19 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-18  3:52 [Bug target/65456] New: " anton at samba dot org
2015-03-18  7:26 ` [Bug target/65456] " trippels at gcc dot gnu.org
2015-03-18  7:34 ` [Bug target/65456] [5 Regression] " trippels at gcc dot gnu.org
2015-03-18  7:50 ` [Bug target/65456] " trippels at gcc dot gnu.org
2015-03-18 11:29 ` rguenth at gcc dot gnu.org
2015-03-18 23:23 ` dje at gcc dot gnu.org
2015-03-19 19:25 ` msebor at gcc dot gnu.org
2015-03-19 22:52 ` anton at samba dot org
2015-03-20 14:47 ` wschmidt at gcc dot gnu.org
2015-03-22 16:59 ` wschmidt at gcc dot gnu.org
2015-03-23  4:21 ` dje at gcc dot gnu.org
2015-03-23 13:50 ` wschmidt at gcc dot gnu.org
2015-03-28  2:19 ` wschmidt at gcc dot gnu.org
2015-03-28 11:40 ` amodra at gmail dot com [this message]
2015-03-29 18:24 ` wschmidt at gcc dot gnu.org
2015-03-29 19:30 ` wschmidt at gcc dot gnu.org
2015-04-23  0:22 ` wschmidt at gcc dot gnu.org
2015-04-23 21:04 ` wschmidt at gcc dot gnu.org
2015-04-24 13:45 ` wschmidt at gcc dot gnu.org
2015-04-24 20:17 ` wschmidt at gcc dot gnu.org
2015-04-24 20:46 ` wschmidt at gcc dot gnu.org
2015-05-04 14:50 ` ro at gcc dot gnu.org
2015-05-04 14:51 ` ro at gcc dot gnu.org
2015-05-04 20:56 ` wschmidt at gcc dot gnu.org
2015-05-05 13:37 ` ro at CeBiTec dot Uni-Bielefeld.DE
2015-05-06 11:34 ` ro at CeBiTec dot Uni-Bielefeld.DE
2015-05-06 12:07 ` wschmidt at gcc dot gnu.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=bug-65456-4-74hFQPFXy2@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: 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).