On 2019/8/13 10:22, luoxhu wrote:
diff --git a/gcc/testsuite/gcc.dg/pr91287.c
b/gcc/testsuite/gcc.dg/pr91287.c
new file mode 100644
index 000..c816e0537aa
--- /dev/null
+++ b/gcc/testsuite/gcc.dg/pr91287.c
@@ -0,0 +1,40 @@
+/* { dg-do assemble } */
+/* { dg-options "-O2" } */
You
We can implement these for TARGET_MMX_WITH_SSE and TARGET_SSE4_1.
2019-08-13 Uroš Bizjak
* config/i386/i386.md (ix86_expand_vector_set) :
Use vec_merge path for TARGET_MMX_WITH_SSE && TARGET_SSE4_1.
: Ditto.
* config/i386/mmx.md (*mmx_pinsrd): New insn pattern.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91431
Bug ID: 91431
Summary: Using class template for containers and iterators
rather than defining template only for iterators
caused a trouble
Product: gcc
Version:
Hi Richard,
On 2019/8/12 16:51, Richard Biener wrote:
On Mon, Aug 12, 2019 at 8:50 AM luoxhu wrote:
Hi Richard,
Thanks for your comments, updated the v2 patch as below:
1. Define and use builtin_with_linkage_p.
2. Add comments.
3. Add a testcase.
In LTO mode, if static library and dynamic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87150
--- Comment #24 from Jason Merrill ---
(In reply to Marek Polacek from comment #23)
> Thanks, missed that. Looks like Jason wants us to fix it retroactively,
> too. I suppose we should just revert my r264172.
Better to disable the section in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91430
Bug ID: 91430
Summary: ICE in curr_insn_transform, at lra-constraints.c:3962
Product: gcc
Version: 9.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
The attached patch ahs been regression tested on x86_64-*-freebsd.
It probably borders on obvious, but I'll ask away. OK to commit?
2019-08-12 Steven G. Kargl
PR fortran/87993
* expr.c (gfc_simplify_expr): Simplifcation of an array with a kind
type inquiry suffix
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91425
--- Comment #8 from joseph at codesourcery dot com ---
A more general representation would facilitate implementing
__builtin_iseqsig (bug 77928).
(As noted in previous discussions, some processors, e.g. MIPS, actually
have a general
On 8/12/19 4:17 PM, Martin Sebor wrote:
> On 8/12/19 2:04 PM, Jeff Law wrote:
>> On 8/9/19 4:14 PM, Martin Sebor wrote:
>>> On 8/9/19 10:58 AM, Jakub Jelinek wrote:
On Fri, Aug 09, 2019 at 10:51:09AM -0600, Martin Sebor wrote:
> That said, we should change this code one way or the other.
On 8/12/19 12:43 PM, Aldy Hernandez wrote:
> This is a fresh re-post of:
>
> https://gcc.gnu.org/ml/gcc-patches/2019-07/msg6.html
>
> Andrew gave me some feedback a week ago, and I obviously don't remember
> what it was because I was about to leave on PTO. However, I do remember
> I
On 8/12/19 12:48 PM, Aldy Hernandez wrote:
> This is a ping of:
>
> https://gcc.gnu.org/ml/gcc-patches/2019-07/msg8.html
>
> I have addressed the comments Jeff mentioned there.
>
> This patch goes before the VR_VARYING + types patch, but I can adapt
> either one to come first. I can even
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87150
--- Comment #23 from Marek Polacek ---
Thanks, missed that. Looks like Jason wants us to fix it retroactively, too.
I suppose we should just revert my r264172.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89413
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |WAITING
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87150
Richard Smith changed:
What|Removed |Added
CC||richard-gccbugzilla@metafoo
On 8/12/19 2:14 PM, Matthew Beliveau wrote:
> This patch improves DSE to handle missing optimizations for zero
> initializations.
>
> Thank you,
> Matthew Beliveau
>
>
> DSE.patch
>
> Bootstrapped/regtested on x86_64-linux, ok for trunk?
>
> 2019-08-12 Matthew Beliveau
>
> PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91109
--- Comment #13 from Bernd Edlinger ---
Created attachment 46704
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46704=edit
another untested patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89647
--- Comment #3 from kargl at gcc dot gnu.org ---
Patch submitted.
The attached patch fixes PR fortran/89647, and has been
regression tested on x86_64-*-freebsd.
If a procedure is made accessible by host association, the
that procedure can be used as binding target. During the
resolution of a type bound procedure, gfortran needs to
check the parent namespace
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91359
--- Comment #18 from Brian T. Carcich ---
Thanks for the fix and your patience.
We got gfortran with this patch to build on a box running Linux 2.6.9 ca.
November 2011, and it solved the problem.
Well done.
The bootstrap succeeded.
On Mon, Aug 12, 2019 at 11:51 AM Caroline Tice wrote:
>
> Hi,
>
> This patch is to fix a bug where linking with -fvtable-verify and
> -static causes the linker to complain about multiple definitions of
> things in the vtv_end*.o files (once from the .o file and once
On 8/12/19 2:04 PM, Jeff Law wrote:
On 8/9/19 4:14 PM, Martin Sebor wrote:
On 8/9/19 10:58 AM, Jakub Jelinek wrote:
On Fri, Aug 09, 2019 at 10:51:09AM -0600, Martin Sebor wrote:
That said, we should change this code one way or the other.
There is even less of a guarantee that other compilers
On 8/9/19 10:17 AM, Martin Sebor wrote:
> GCC 9 optimizes a subset of expression of the form
> (0 == strcmp(a, b)) based on the length and/or size of
> the arguments but it doesn't take advantage of all
> the opportunities there. For example in the following,
> although it folds the first test to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47191
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33056
Bug 33056 depends on bug 47191, which changed state.
Bug 47191 Summary: Misleading error message if part-ref starts with DATA
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47191
What|Removed |Added
Hello-
The attached patch for libcpp adds support for extended characters (e.g. UTF-8)
in identifiers. A preliminary version of the patch was posted on PR c/67224 as
Comment 26 (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224#c26) and
discussed with Joseph Myers. Here is an updated patch
On Tue, 11 Jun 2019, Bruce Korb wrote:
> I should probably update the e-address as well. Yes, I still receive
> gnu.org email, but not daily. As infrequent as monthly. Can I do
> something to auto-forward it to an e-address I process daily?
You can log in to fencepost.gnu.org and edit
On Mon, Aug 12, 2019 at 09:20:18PM +, Joseph Myers wrote:
> On Mon, 12 Aug 2019, Segher Boessenkool wrote:
>
> > (define_insn "add_truncdfsf3"
> > [(set (match_operand:SF 0 "gpc_reg_operand" "=f,wa")
> > (float_truncate:SF
> > (plus:DF (match_operand:DF 1 "gpc_reg_operand"
On Mon, 12 Aug 2019, Segher Boessenkool wrote:
> (define_insn "add_truncdfsf3"
> [(set (match_operand:SF 0 "gpc_reg_operand" "=f,wa")
> (float_truncate:SF
> (plus:DF (match_operand:DF 1 "gpc_reg_operand" "%d,wa")
> (match_operand:DF 2 "gpc_reg_operand" "d,wa"]
On 8/8/19 6:17 AM, Jozef Lawrynowicz wrote:
> This patch extends the MCU data handling so that MCU data can be provided
> in an external file (devices.csv). This means the compiler doesn't have to be
> updated and rebuilt to support new devices when they are released.
>
> TI distribute
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90538
Jason Merrill changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91378
Jason Merrill changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
On 8/8/19 6:14 AM, Jozef Lawrynowicz wrote:
> This patch improves the handling of MCU data by consolidating multiple
> copies of hard-coded MCU data into a single location, and adds a new function
> to be used as a single entry point for the extraction of MCU data for the
> selected MCU.
>
> This
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87150
--- Comment #21 from Jason Merrill ---
(In reply to Jason Merrill from comment #19)
> And now P1155/P1825 removes that text, so in C++20 mode the original
> testcase needs to call the move constructor again.
Actually, it's a DR, so not just
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91429
Bug ID: 91429
Summary: Conditional explicit not respected with out-of-line
definition
Product: gcc
Version: 9.1.0
Status: UNCONFIRMED
Severity: normal
On Sun, Aug 11, 2019 at 12:37:49PM +0300, Janne Blomqvist wrote:
> Update the PRNG from xorshift1024* to xoshiro256** by the same
> author. For details see
>
> http://prng.di.unimi.it/
>
> and the paper at
>
> https://arxiv.org/abs/1805.01407
>
> Also the seeding is slightly improved, by
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91422
--- Comment #3 from Thomas Koenig ---
Author: tkoenig
Date: Mon Aug 12 20:21:37 2019
New Revision: 274320
URL: https://gcc.gnu.org/viewcvs?rev=274320=gcc=rev
Log:
2019-08-12 Thomas Koenig
PR fortran/91424
* frontend-passes.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91424
--- Comment #5 from Thomas Koenig ---
Author: tkoenig
Date: Mon Aug 12 20:21:37 2019
New Revision: 274320
URL: https://gcc.gnu.org/viewcvs?rev=274320=gcc=rev
Log:
2019-08-12 Thomas Koenig
PR fortran/91424
* frontend-passes.c
I have no comments on the patch itself, but...
On Mon, Aug 12, 2019 at 04:14:40PM -0400, Matthew Beliveau wrote:
> 2019-08-12 Matthew Beliveau
>
> PR c++/DSE.patch
Please drop this.
> * tree-ssa-dse.c (dse_optimize_redundant_stores): Improved check to
> catch more
On 8/6/19 1:58 AM, senthilkumar.selva...@microchip.com wrote:
> Hi,
>
> r254484 explicitly added previously ignored address space
> qualifiers, when
> emitting DWARF dies for types.
>
> Adding address spaces to cv_qual_mask, however, breaks
> nearest_type_subqualifier, which uses the
This patch improves DSE to handle missing optimizations for zero
initializations.
Thank you,
Matthew Beliveau
Bootstrapped/regtested on x86_64-linux, ok for trunk?
2019-08-12 Matthew Beliveau
PR c++/DSE.patch
* tree-ssa-dse.c (dse_optimize_redundant_stores): Improved check to
catch more
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91359
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91359
--- Comment #16 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Mon Aug 12 20:09:00 2019
New Revision: 274319
URL: https://gcc.gnu.org/viewcvs?rev=274319=gcc=rev
Log:
2019-08-12 Steven G. Kargl
PR fortran/91359
*
On 8/12/19 8:48 AM, Jakub Jelinek wrote:
> Hi!
>
> The following patch adds some tweaks for -Wsequence-point warning for C++17
> and later. In particular, stop warning about no sequence point in between
> <<, >>, ., -> and [] expressions, where E1 is in C++17 sequenced before E2.
>
>
On 8/9/19 4:14 PM, Martin Sebor wrote:
> On 8/9/19 10:58 AM, Jakub Jelinek wrote:
>> On Fri, Aug 09, 2019 at 10:51:09AM -0600, Martin Sebor wrote:
>>> That said, we should change this code one way or the other.
>>> There is even less of a guarantee that other compilers support
>>> writing past the
On Mon, Aug 12, 2019 at 05:18:18PM +0200, Thomas Koenig wrote:
> Hello world,
>
> the attached patch fixes three problems with DO loop index warnings:
>
> - DO loops in contained procedures were not checked
>
> - Zero-trip loops gave a false positive
>
> - DO loops in blocks gave the same
On 8/9/19 5:42 PM, Martin Sebor wrote:
>>> @@ -3408,7 +3457,13 @@ static bool
>>> }
>>> gimple *stmt = SSA_NAME_DEF_STMT (exp);
>>> - if (gimple_code (stmt) != GIMPLE_PHI)
>>> + if (gimple_assign_single_p (stmt))
>>> + {
>>> + tree rhs = gimple_assign_rhs1 (stmt);
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91428
--- Comment #2 from Marek Polacek ---
*be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91428
Marek Polacek changed:
What|Removed |Added
Keywords||diagnostic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91407
--- Comment #4 from Aso Renji ---
(In reply to Jonathan Wakely from comment #3)
> But it's not enabled by -Wall7
>
> Maybe QtCreator should be fixed instead.
Hmm, compile output in QtCreator:
g++ -c -pipe -g -Wall -W -fPIC -DQT_QML_DEBUG
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42546
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89078
Bug 89078 depends on bug 42546, which changed state.
Bug 42546 Summary: ALLOCATED statement typo in the docs and for scalar variables
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42546
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42546
--- Comment #7 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Mon Aug 12 19:48:37 2019
New Revision: 274318
URL: https://gcc.gnu.org/viewcvs?rev=274318=gcc=rev
Log:
2019-08-01 Steven G. Kargl
PR fortran/42546
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91428
Bug ID: 91428
Summary: Please warn on if constexpr
(std::is_constant_evaluated())
Product: gcc
Version: 9.1.0
Status: UNCONFIRMED
Severity: normal
On 8/12/19 8:34 PM, Pedro Alves wrote:
> Let me share my 2c -- the format GDB uses doesn't affect most GCC forks
I meant most GCC folks.
Thanks,
Pedro Alves
On 8/1/19 4:01 PM, Jakub Jelinek wrote:
> You can easily tweak the script to handle the other way too.
> Looking around, different people have different style, some people don't
> post the date/name/email lines at all, others do, some people post them
> multiple times, once for each ChangeLog,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90330
--- Comment #31 from Iain Sandoe ---
(In reply to Matt Thompson from comment #30)
> (In reply to Matt Thompson from comment #28)
> > (In reply to Iain Sandoe from comment #27)
> > > That's fine - essentially, you're building them from source and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91407
--- Comment #3 from Jonathan Wakely ---
But it's not enabled by -Wall7
Maybe QtCreator should be fixed instead.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84864
Eric Gallager changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49129
Eric Gallager changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85004
Eric Gallager changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91420
Jim Wilson changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
I missed this one. As a sign of repentance, I'll aim to address it this week.
Applying to CVS.
Index: cxx-status.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/cxx-status.html,v
retrieving revision 1.96
diff -u -r1.96
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77672
Eric Gallager changed:
What|Removed |Added
Status|ASSIGNED|WAITING
CC|
Hi,
This patch is to fix a bug where linking with -fvtable-verify and
-static causes the linker to complain about multiple definitions of
things in the vtv_end*.o files (once from the .o file and once from
libvtv.a). (See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91396).
The fix is for the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91427
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91427
Bug ID: 91427
Summary: Implement P1825R0, Merged wording for P0527R1 and
P1155R3
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90330
--- Comment #30 from Matt Thompson ---
(In reply to Matt Thompson from comment #28)
> (In reply to Iain Sandoe from comment #27)
> > That's fine - essentially, you're building them from source and therefore
> > don't need to worry about
This is a ping of:
https://gcc.gnu.org/ml/gcc-patches/2019-07/msg8.html
I have addressed the comments Jeff mentioned there.
This patch goes before the VR_VARYING + types patch, but I can adapt
either one to come first. I can even munge them together into one
patch, if it helps review.
This is a fresh re-post of:
https://gcc.gnu.org/ml/gcc-patches/2019-07/msg6.html
Andrew gave me some feedback a week ago, and I obviously don't remember
what it was because I was about to leave on PTO. However, I do remember
I addressed his concerns before getting drunk on rum in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87150
--- Comment #20 from Marek Polacek ---
(In reply to Jason Merrill from comment #19)
> And now P1155/P1825 removes that text, so in C++20 mode the original
> testcase needs to call the move constructor again. Marek, I don't see
> P1825R0 in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61257
--- Comment #6 from Tom Tromey ---
(In reply to Eric Gallager from comment #4)
> (In reply to Sergei Trofimovich from comment #3)
> > (In reply to Sergei Trofimovich from comment #2)
> > > Having explicit flags like --enable-systemtap /
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87150
--- Comment #19 from Jason Merrill ---
And now P1155/P1825 removes that text, so in C++20 mode the original testcase
needs to call the move constructor again. Marek, I don't see P1825R0 in
cxx-status.html, was there a reason not to add it?
On Mon, Aug 12, 2019 at 11:01:11PM +0530, Tejas Joshi wrote:
> I have the following code in my rs6000.md (I haven't used new TARGET_* yet) :
>
> (define_expand "add_truncdfsf3"
> [(set (match_operand:SF 0 "gpc_reg_operand")
>(float_truncate:SF
>(plus:DF (match_operand:DF 1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91407
--- Comment #2 from Aso Renji ---
(In reply to Jonathan Wakely from comment #1)
> Is there a reason you need to use -Wnon-virtual-dtor ?
QtCreator with -Wall as default compile option. Yes, I can set custom compile
options, or use #pragma GCC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88095
--- Comment #6 from Jason Merrill ---
Author: jason
Date: Mon Aug 12 17:46:37 2019
New Revision: 274317
URL: https://gcc.gnu.org/viewcvs?rev=274317=gcc=rev
Log:
PR c++/88095, CTAD for literal operator templates per P0732
This patch fixes PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91378
--- Comment #3 from Jason Merrill ---
Author: jason
Date: Mon Aug 12 17:46:32 2019
New Revision: 274316
URL: https://gcc.gnu.org/viewcvs?rev=274316=gcc=rev
Log:
PR c++/91378 - ICE with noexcept and auto return type.
Here, since the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90538
--- Comment #3 from Jason Merrill ---
Author: jason
Date: Mon Aug 12 17:46:25 2019
New Revision: 274315
URL: https://gcc.gnu.org/viewcvs?rev=274315=gcc=rev
Log:
PR c++/90538 - multiple expansions of capture packs
Previously, with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91423
--- Comment #4 from Andrew Pinski ---
Vec size = s.size;
you are invoking the copy constructor here ...
Which means you are taking the address (implicitly).
Hi,
I have the following code in my rs6000.md (I haven't used new TARGET_* yet) :
(define_expand "add_truncdfsf3"
[(set (match_operand:SF 0 "gpc_reg_operand")
(float_truncate:SF
(plus:DF (match_operand:DF 1 "gpc_reg_operand")
(match_operand:DF 2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91418
--- Comment #5 from Harald van Dijk ---
(In reply to Darrell Wright from comment #4)
> The weird part is, other than compilers don't agree, but the lookup finds it
> if you put the template argument in
The idea there seems to be that `class A;`
On Fri, May 31, 2019 at 12:52:32PM +0100, Wilco Dijkstra wrote:
> With -mcpu=generic the function alignment is currently 8, however almost all
> supported cores prefer 16 or higher, so increase the default to 16:12.
> This gives ~0.2% performance increase on SPECINT2017, while codesize is 0.12%
>
On Tue, Jul 30, 2019 at 05:59:15PM +0100, Kyrill Tkachov wrote:
> Hi all,
>
> The neoversen1 tuning struct gives better performance on the Cortex-A76,
> so use that.
> The only difference from the current tuning is the function and label
> alignment settings.
>
> This gives about 1.3%
On Tue, May 28, 2019 at 06:11:29PM +0100, Wilco Dijkstra wrote:
> PR81800 is about the lrint inline giving spurious FE_INEXACT exceptions.
> The previous change for PR81800 didn't fix this: when lrint is disabled
> in the backend, the midend will simply use llrint. This actually makes
> things
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91424
--- Comment #4 from Thomas Koenig ---
(In reply to Eric Gallager from comment #2)
> - the "2" location marker is a different color from the "1" location marker,
> if you have colorized output
That is now PR 91426.
Hi,
On Tue, 30 Jul 2019 15:35:23 +0200
Christophe Lyon wrote:
> Hi,
>
> Thanks for the useful feedback.
>
>
> On Tue, 16 Jul 2019 at 11:54, Richard Sandiford
> wrote:
> >
> > Thanks for doing this in a generic way.
> >
> > Christophe Lyon writes:
> > > @@ -2224,6 +2234,50 @@
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91426
Bug ID: 91426
Summary: Different colors for errors with multiple locations
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
On Wed, Aug 07, 2019 at 07:19:12PM +0100, Richard Sandiford wrote:
> Some indexed SVE FCMLA operations have a 3-bit register field that
> requires one of Z0-Z7. This patch adds a public "y" constraint for that.
>
> The patch also documents "x", which is again intended to be a public
>
On Wed, Aug 07, 2019 at 07:24:18PM +0100, Richard Sandiford wrote:
> aarch64_classify_vector_mode used properties of a mode to test whether
> the mode was a single Advanced SIMD vector, a single SVE vector, or a
> tuple of SVE vectors. That works well for current trunk and is simpler
> than
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83250
--- Comment #8 from Jakub Jelinek ---
Intrinsics now implemented for GCC 10+, keeping open for some optimizations.
On Wed, Aug 07, 2019 at 08:23:48PM +0100, Richard Sandiford wrote:
> The Advanced SIMD and SVE permute patterns both split the permute
> operation into a base name and a hilo suffix. That works well, but it
> means that for "@" patterns, we need to pass the permute code twice,
> once for the base
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90361
--- Comment #8 from Jonathan Wakely ---
Author: redi
Date: Mon Aug 12 16:41:27 2019
New Revision: 274314
URL: https://gcc.gnu.org/viewcvs?rev=274314=gcc=rev
Log:
PR libstdc++/90361 add missing macro definition
The src/c++17/string-inst.cc file
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69558
Eric Gallager changed:
What|Removed |Added
Target Milestone|9.3 |8.5
--- Comment #30 from Eric Gallager
The src/c++17/string-inst.cc file needs to override the default string
ABI so that it still contains the expected symbols even when the library
is configured with --with-default-libstdcxx-abi=gcc4-compatible.
PR libstdc++/90361
* src/c++17/string-inst.cc: Use
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77711
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|9.3 |10.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91424
--- Comment #3 from Thomas Koenig ---
(In reply to Eric Gallager from comment #2)
> Also:
> - there's no option flag controlling the warning
That one is by design. There is no way that this can even
be valid code.
> - the "2" location marker
On Mon, Aug 12, 2019 at 10:27:46AM -0600, Martin Sebor wrote:
> FWIW, another feature I find useful that mklog doesn't seem to have
> is one that strips the context details from testsuite ChangeLogs.
> Hardly anyone bothers to mention the functions, macros, types, or
> variables they changed in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91424
Eric Gallager changed:
What|Removed |Added
Keywords||diagnostic
CC|
On 8/2/19 12:04 AM, Martin Liška wrote:
On 8/2/19 7:45 AM, Martin Liška wrote:
I agree with that approach.
I'm sending an example how it would look like for something
bigger:
$ git diff
e8a3be407068bfb9c82f0f6656b30d26cc2f484a~15..e8a3be407068bfb9c82f0f6656b30d26cc2f484a >
patch &&
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90330
--- Comment #29 from Matt Thompson ---
Also, this did seem to build GCC:
CC="/Users/mathomp4/installed/Core/gcc-gfortran/8.2.0/bin/gcc
--sysroot=/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90330
--- Comment #28 from Matt Thompson ---
(In reply to Iain Sandoe from comment #27)
> That's fine - essentially, you're building them from source and therefore
> don't need to worry about --with-gmp= configure options etc.
>
> For the record, I'm
1 - 100 of 411 matches
Mail list logo
