on 2019/5/6 上午9:50, Bin.Cheng wrote:
> On Sun, May 5, 2019 at 2:02 PM Kewen.Lin wrote:
>>
>> To decrease the cost isn't workable for this case, it make the original
>> iv cand is preferred more and over the other iv cand for memory iv use,
>> then the desirable memory based iv cand won't be chosen
Tested on x86_64-unknown-linux-gnu and ppc64le-linux.
Richard.
2019-05-06 Richard Biener
PR testsuite/90331
* gcc.dg/pr87314-1.c: Align the substring to open up
string merging for targets aligning strings to 8 bytes.
Index: gcc/testsuite/gcc.dg/pr87314-1.c
=
On 5/2/19 2:31 PM, Richard Biener wrote:
> On Mon, Apr 29, 2019 at 2:51 PM Martin Liška wrote:
>>
>> On 4/26/19 3:18 PM, Richard Biener wrote:
>>> On Wed, Apr 10, 2019 at 10:12 AM Martin Liška wrote:
On 4/9/19 3:19 PM, Jan Hubicka wrote:
>> Hi.
>>
>> There's updated version
Hi.
The patch is about support of a new GIMPLE expr.
Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
Ready to be installed?
Thanks,
Martin
>From a4f23fe8d876f2d8a0628feb57127e276348aab0 Mon Sep 17 00:00:00 2001
From: marxin
Date: Fri, 3 May 2019 13:54:40 +0200
Subject: [P
Hi!
On Tue, 31 Jul 2018 08:12:51 -0700, Cesar Philippidis
wrote:
> This is an old patch which removes the struct map from the nvptx plugin.
(This got committed to trunk in r263212.)
> I believe at one point this was supposed to be used to manage async data
> mappings, but in practice that neve
The attached patch fix pr90357, bootstraped and regressed test on
mips64el-linux-gnu target.
Ok for commit ?
From a3db8763ee8460a5f63c567d58624a985f9924ce Mon Sep 17 00:00:00 2001
From: Chenghua Xu
Date: Mon, 6 May 2019 16:14:56 +0800
Subject: [PATCH] [PATCH,MIPS] Skip forward src into next insn w
Hi!
On Wed, 20 Apr 2016 12:27:27 +0200, Jakub Jelinek wrote:
> On Wed, Apr 20, 2016 at 10:46:38AM +0200, Thomas Schwinge wrote:
> > Clean up libgomp GCC 5 legacy support
> >
> > libgomp/
> > * config/nvptx/oacc-parallel.c: Empty file.
| * oacc-parall
Hi,
one of most straightforward changes in my pending queue. Tested
x86_64-linux.
Thanks, Paolo.
/
2019-05-06 Paolo Carlini
* call.c (build_call_a): Use FUNC_OR_METHOD_TYPE_P.
* cp-gimplify.c (cp_fold): Likewise.
* cp-objcp-common.c (cp_type_dw
Another restrict issue hitting both vectorization and loop distribution.
Bootstrap / regtest running on x86_64-unknown-linux-gnu.
Richard.
2019-05-06 Richard Biener
PR tree-optimization/90328
* tree-data-ref.h (dr_may_alias_p): Pass in the actual loop nest.
* tree-d
On Sat, 4 May 2019, Richard Sandiford wrote:
> Richard Biener writes:
> > On Fri, 3 May 2019, Richard Biener wrote:
> >
> >>
> >> I am testing the following patch to remove the code determining
> >> the target virtual operand to walk to and instead compute it
> >> based on the immediate dominato
On Thu, Mar 21, 2019 at 5:57 AM JunMa wrote:
>
> Hi
> For now, gcc can not fold code like:
>
> const char a[5] = "123"
> __builtin_memchr (a, '7', sizeof a)
>
> It tries to avoid folding out of string length although length of a is 5.
> This is a bit conservative, it's safe to folding memchr/bcmp/
On Sun, May 5, 2019 at 8:03 AM bin.cheng wrote:
>
> > --
> > Sender:Jakub Jelinek
> > Sent At:2019 Apr. 17 (Wed.) 19:27
> > Recipient:Bin.Cheng
> > Cc:bin.cheng ; GCC Patches
> >
> > Subject:Re: [PATCH PR90078]Capping comp_cost co
On Mon, May 6, 2019 at 5:04 AM Feng Xue OS wrote:
>
> Hi Richard,
>
>
>Since gcc 9 has been released, will you get some time to take a look at
> this patch? Thanks.
I'm working through the backlog but I also hope Micha can have a look
here since he
authored the loop splitting code.
Richard.
On Sun, 5 May 2019, Kewen.Lin wrote:
> on 2019/4/27 上午11:44, Bin.Cheng wrote:
> > GCC lacks the capability passing information to later passes. Gimple
> > analyzer worked hard collecting various information but discards it
> > entering RTL or earlier. Other examples are like runtime alias
> > in
On Fri, May 03, 2019 at 12:47:39PM +0200, Richard Biener wrote:
> On Wed, Dec 12, 2018 at 11:54 AM Richard Biener wrote:
> >
> >
> > The following improves x264 vectorization by avoiding peeling for gaps
> > noticing that when the upper half of a vector is unused we can
> > load the lower part onl
On Mon, May 6, 2019 at 6:11 PM Richard Biener
wrote:
>
> On Sun, May 5, 2019 at 8:03 AM bin.cheng wrote:
> >
> > > --
> > > Sender:Jakub Jelinek
> > > Sent At:2019 Apr. 17 (Wed.) 19:27
> > > Recipient:Bin.Cheng
> > > Cc:bin.cheng ;
On Fri, May 3, 2019 at 6:41 PM H.J. Lu wrote:
>
> simplify_vector_constructor has
>
> constructor_elt *elt;
> ...
> FOR_EACH_VEC_SAFE_ELT (CONSTRUCTOR_ELTS (op), i, elt)
> {
> ...
> unsigned int elt;
> ...
> }
>
> This patch renames the second elt to elem to avoid sha
On Mon, May 6, 2019 at 12:24 PM Bin.Cheng wrote:
>
> On Mon, May 6, 2019 at 6:11 PM Richard Biener
> wrote:
> >
> > On Sun, May 5, 2019 at 8:03 AM bin.cheng
> > wrote:
> > >
> > > > --
> > > > Sender:Jakub Jelinek
> > > > Sent At:
On Mon, 6 May 2019, Jakub Jelinek wrote:
> On Fri, May 03, 2019 at 12:47:39PM +0200, Richard Biener wrote:
> > On Wed, Dec 12, 2018 at 11:54 AM Richard Biener wrote:
> > >
> > >
> > > The following improves x264 vectorization by avoiding peeling for gaps
> > > noticing that when the upper half of
On Sun, 5 May 2019 at 08:31, Li Jia He wrote:
>
> Hi,
>
> GCC revision 267634 implemented two_value_replacement function.
> However, a typo occurred during the parameter check, which caused
> us to miss some optimizations.
>
> The intent of the code might be to check that the input parameters
> ar
This patch adds static asserts for type traits misuse with incomplete
classes and unions. This gives a nice readable error message instead
of an UB and odr-violations.
Some features of the patch:
* each type trait has it's own static_assert inside. This gives better
diagnostics than the approach w
On Sun, May 5, 2019 at 11:09 PM Eric Botcazou wrote:
>
> > I have now applied this variant.
>
> You backported it onto the 8 branch on Friday:
>
> 2019-05-03 Richard Biener
>
> Backport from mainline
> [...]
> 2019-03-07 Richard Biener
>
> PR tree-optimization/89595
>
I have some patches to mkdeps, but first this one renames the rather
bland 'struct deps' to 'struct mkdeps'. (discovered when I made myself
a local 'struct deps')
[mkdeps at least matches the file name, even though it's going to become
non make-specific.]
nathan
--
Nathan Sidwell
2019-05-06
On Mon, May 6, 2019 at 10:00 AM Martin Liška wrote:
>
> Hi.
>
> The patch is about support of a new GIMPLE expr.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
> Ready to be installed?
Can you please avoid using/changing parser_build_binary_op? The other
binary expr
On Mon, May 06, 2019 at 01:19:15PM +0200, Christophe Lyon wrote:
> > The regression testing for the patch was done on GCC mainline on
> >
> > powerpc64le-unknown-linux-gnu (Power 9 LE)
> >
> > with no regressions. Is it OK for trunk and backport to gcc 9 ?
While the posted patch had:
> > +/*
在 2019/5/6 下午6:02, Richard Biener 写道:
On Thu, Mar 21, 2019 at 5:57 AM JunMa wrote:
Hi
For now, gcc can not fold code like:
const char a[5] = "123"
__builtin_memchr (a, '7', sizeof a)
It tries to avoid folding out of string length although length of a is 5.
This is a bit conservative, it's saf
On 2019/5/6 7:35 PM, Jakub Jelinek wrote:
On Mon, May 06, 2019 at 01:19:15PM +0200, Christophe Lyon wrote:
The regression testing for the patch was done on GCC mainline on
powerpc64le-unknown-linux-gnu (Power 9 LE)
with no regressions. Is it OK for trunk and backport to gcc 9 ?
Whil
On Mon, May 06, 2019 at 08:22:41PM +0800, Li Jia He wrote:
> > Dunno why this changed, if you want it in phiopt1, you need "phiopt1"
> > in scan-tree-dump-not as well, if you want optimized dump, you need
> > -fdump-tree-optimized instead.
> When I test the code again for submiting the code, I foun
Hi,
this patch makes aliasing_component_refs_p little bit stronger, especially
with LTO increasing number of disambiguations on tramp3d by 2%.
It took me a while to uderstand that function so a bit summary what it
does.
Function analyzes chains of nested references like
ref1: a.b.c.d.e
ref2: c
On 2019/5/6 8:27 PM, Jakub Jelinek wrote:
On Mon, May 06, 2019 at 08:22:41PM +0800, Li Jia He wrote:
Dunno why this changed, if you want it in phiopt1, you need "phiopt1"
in scan-tree-dump-not as well, if you want optimized dump, you need
-fdump-tree-optimized instead.
When I test the code a
On Fri, 3 May 2019, H.J. Lu wrote:
> On Fri, May 3, 2019 at 6:02 AM Richard Biener wrote:
> >
> >
> > The following refactors simplify_vector_constructor and adds
> > handling of constants to it in a straight-forward way.
> >
> > A followup will handle the testcases posted in HJs patch.
...
> > -
Better late than never: here's the gcc-9/changes.html update listing
Solaris improvements. I'm all ears for suggestions about wording or
markup improvements.
Ok?
Thanks.
Rainer
--
-
Rainer Orth, Center for Biot
On Mon, 6 May 2019, Jan Hubicka wrote:
> Hi,
> this patch makes aliasing_component_refs_p little bit stronger, especially
> with LTO increasing number of disambiguations on tramp3d by 2%.
>
> It took me a while to uderstand that function so a bit summary what it
> does.
>
> Function analyzes cha
On 5/2/19 9:04 PM, Richard Biener wrote:
> On May 2, 2019 8:14:46 PM GMT+02:00, Segher Boessenkool
> wrote:
>> On Thu, May 02, 2019 at 07:41:18PM +0200, Richard Biener wrote:
>>> On May 2, 2019 7:00:16 PM GMT+02:00, Segher Boessenkool
>> wrote:
On Thu, May 02, 2019 at 03:18:00PM +0200, Rich
On 5/2/19 3:18 PM, Richard Biener wrote:
> On Mon, 29 Apr 2019, Martin Liška wrote:
>
>> On 9/10/18 1:43 PM, Martin Liška wrote:
>>> On 09/04/2018 05:07 PM, Martin Liška wrote:
- in order to achieve real speed up we need to split also other generated
(and also dwarf2out.c, i386.c, ..) f
I sent the fix for 90363 previously with the FPU patches. Now, I have added
tests and another issue came up, so I am sending as a new series. I planned to
commit the code before the 9.x release but missed that.
This is a series of fixes for the OpenRISC target found during recent testings.
PRs:
Volatile memory does not match the memory_operand predicate. This
causes extra extend/mask instructions instructions when reading
from volatile memory. On OpenRISC loading volitile memory can be
treated the same as regular memory loads which supports combined
sign/zero extends. Fixing this elimi
As reported by Richard Selvaggi. Also, add a basic test to verify the
soft math works when enabled.
gcc/testsuite/ChangeLog:
PR target/90362
* gcc.target/or1k/div-mul-3.c: New test.
libgcc/ChangeLog:
PR target/90362
* config/or1k/lib1funcs.S (__udivsi3): Change
Hi!
The following patch adds some store-merging improvements.
Previously, only stores where the lhs was
ARRAY_REF, ARRAY_RANGE_REF, MEM_REF, COMPONENT_REF or BIT_FIELD_REF
were considered, as the testcases show it is useful to consider
stores into whole decl as well.
Another thing is that we were
On 2019/5/6 7:19 PM, Christophe Lyon wrote:
On Sun, 5 May 2019 at 08:31, Li Jia He wrote:
Hi,
GCC revision 267634 implemented two_value_replacement function.
However, a typo occurred during the parameter check, which caused
us to miss some optimizations.
The intent of the code might be to
On Mon, 6 May 2019, Martin Liška wrote:
> On 5/2/19 3:18 PM, Richard Biener wrote:
> > On Mon, 29 Apr 2019, Martin Liška wrote:
> >
> >> On 9/10/18 1:43 PM, Martin Liška wrote:
> >>> On 09/04/2018 05:07 PM, Martin Liška wrote:
> - in order to achieve real speed up we need to split also other
On Mon, 6 May 2019, Martin Liška wrote:
> On 5/2/19 9:04 PM, Richard Biener wrote:
> > On May 2, 2019 8:14:46 PM GMT+02:00, Segher Boessenkool
> > wrote:
> >> On Thu, May 02, 2019 at 07:41:18PM +0200, Richard Biener wrote:
> >>> On May 2, 2019 7:00:16 PM GMT+02:00, Segher Boessenkool
> >> wrote
The following fixes a miscompilation by the recent vector load
optimization. The check matching unused upper half of a vector
was incomplete.
Bootstrap / regtest running on x86_64-unknown-linux-gnu, applied to trunk.
Richard.
2019-05-06 Richard Biener
PR tree-optimization/90358
Hi.
The patch append to target_gtfiles at 3 places instead of overwriting
that.
Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
Ready to be installed?
Thanks,
Martin
gcc/ChangeLog:
2019-05-06 Martin Liska
* config.gcc: Append to target_gtfiles.
---
gcc/confi
On 5/6/19 3:31 PM, Richard Biener wrote:
> On Mon, 6 May 2019, Martin Liška wrote:
>
>> On 5/2/19 3:18 PM, Richard Biener wrote:
>>> On Mon, 29 Apr 2019, Martin Liška wrote:
>>>
On 9/10/18 1:43 PM, Martin Liška wrote:
> On 09/04/2018 05:07 PM, Martin Liška wrote:
>> - in order to achi
On 5/6/19 3:36 PM, Richard Biener wrote:
> On Mon, 6 May 2019, Martin Liška wrote:
>
>> On 5/2/19 9:04 PM, Richard Biener wrote:
>>> On May 2, 2019 8:14:46 PM GMT+02:00, Segher Boessenkool
>>> wrote:
On Thu, May 02, 2019 at 07:41:18PM +0200, Richard Biener wrote:
> On May 2, 2019 7:00:1
On Mon, May 06, 2019 at 03:47:53PM +0200, Martin Liška wrote:
> The patch append to target_gtfiles at 3 places instead of overwriting
> that.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
> Ready to be installed?
> Thanks,
> Martin
>
> gcc/ChangeLog:
>
> 2019-05-0
On 5/6/19 3:52 PM, Jakub Jelinek wrote:
> On Mon, May 06, 2019 at 03:47:53PM +0200, Martin Liška wrote:
>> The patch append to target_gtfiles at 3 places instead of overwriting
>> that.
>>
>> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>>
>> Ready to be installed?
>> Than
Hi.
I'm sending following backport that I've just tested.
Martin
>From ad56099403b078303477e3f501ef09b2e2b6e450 Mon Sep 17 00:00:00 2001
From: marxin
Date: Mon, 6 May 2019 07:35:59 +
Subject: [PATCH] Backport r270899
gcc/ChangeLog:
2019-05-06 Martin Liska
PR sanitizer/90312
* config/
On Mon, May 6, 2019 at 9:59 AM Martin Liška wrote:
>
> On 5/2/19 2:31 PM, Richard Biener wrote:
> > On Mon, Apr 29, 2019 at 2:51 PM Martin Liška wrote:
> >>
> >> On 4/26/19 3:18 PM, Richard Biener wrote:
> >>> On Wed, Apr 10, 2019 at 10:12 AM Martin Liška wrote:
>
> On 4/9/19 3:19 PM,
On Fri, 3 May 2019, Jakub Jelinek wrote:
> Hi!
>
> I'd like to ping this patch for stage1.
> Bootstrapped/regtested it again last night successfully.
>
> On Fri, Feb 08, 2019 at 08:36:33AM +0100, Jakub Jelinek wrote:
> > The following patch uses a simple data flow to find live (addressable)
> >
Hi,
This patch implements the optimization in PR77820. The optimization
eliminates phi and phi's basic block, if the phi is used only by
condition branch, and the phi's incoming value in the result of a
CMP result.
This optimization eliminates:
1. saving CMP result: p0 = a CMP b.
2. additional C
On Mon, Feb 11, 2019 at 9:25 AM Rainer Orth
wrote:
>
> Hi Uros,
>
> > On Fri, Feb 8, 2019 at 1:24 PM Uros Bizjak wrote:
> >
> >> Attached patch fixes --enable-frame-pointer handling, and this way
> >> makes a couple of defines in config/i386/sol2.h obsolete.
> >
> > It turned out that --enable-f
On Mon, May 06, 2019 at 03:36:06PM +0200, Richard Biener wrote:
> On Mon, 6 May 2019, Martin Liška wrote:
> > 2) faster bootstrap on a massively parallel machine (64+ cores)
>
> I guess for this we can also try to do LTO bootstap and
> LTO-link libbackend itself. LTO bootstrap is only slow becaus
On Mon, May 06, 2019 at 04:17:01PM +0200, Richard Biener wrote:
> > > + vec active;
> > > + /* Work bitmap of currently live variables. */
> > > + bitmap work;
> > > + /* Bitmap of interesting variables. Variables with uids not in this
> > > + bitmap are not tracked. */
> > > + bitmap v
This new code
vec_safe_push (call_args, (*call_args)[nargs-1]);
doesn't seem to work well because "obj" points to garbage after the
vec_safe_reserve
call:
template
inline T *
vec_safe_push (vec *&v, const T &obj CXX_MEM_STAT_INFO)
{
vec_safe_reserve (v, 1, false PASS_MEM_STAT);
return v->
On Mon, May 6, 2019 at 12:32 PM Marek Polacek wrote:
>
> This new code
>
> vec_safe_push (call_args, (*call_args)[nargs-1]);
>
> doesn't seem to work well because "obj" points to garbage after the
> vec_safe_reserve
> call:
>
> template
> inline T *
> vec_safe_push (vec *&v, const T &obj CXX_ME
On Mon, May 06, 2019 at 04:17:01PM +0200, Richard Biener wrote:
> > > +/* Data structure for compute_live_vars* functions. */
> > >
> > > +struct compute_live_vars_data {
> > > + /* Vector of bitmaps for live vars at the end of basic blocks,
> > > + indexed by bb->index. ACTIVE[ENTRY_BLOCK
Hi
This is another attempt to make adapter iterator types operators
undefined when underlying iterator type doesn't support it. For the
move_iterator it is rather easy and even already done for the operator-
so I just generalize it to comparison operators. It doesn't cover all
operators o
On Mon, 6 May 2019, Rainer Orth wrote:
> Better late than never: here's the gcc-9/changes.html update listing
> Solaris improvements. I'm all ears for suggestions about wording or
> markup improvements.
I believe it should be "runtime library", cf.
https://gcc.gnu.org/codingconventions.html .
A
On 5/6/19 5:58 AM, JunMa wrote:
在 2019/5/6 下午6:02, Richard Biener 写道:
On Thu, Mar 21, 2019 at 5:57 AM JunMa wrote:
Hi
For now, gcc can not fold code like:
const char a[5] = "123"
__builtin_memchr (a, '7', sizeof a)
It tries to avoid folding out of string length although length of a
is 5.
T
The recent LTO patches broke Solaris bootstrap (both sparc and x86):
/vol/gcc/src/hg/trunk/local/gcc/lto/lto-common.c: In function
'lto_file_decl_data* lto_file_read(lto_file*, std::FILE*, int*)':
/vol/gcc/src/hg/trunk/local/gcc/lto/lto-common.c:2114:32: error: format '%ld'
expects argument of t
On May 6, 2019 8:35:15 PM GMT+02:00, Rainer Orth
wrote:
>The recent LTO patches broke Solaris bootstrap (both sparc and x86):
>
>/vol/gcc/src/hg/trunk/local/gcc/lto/lto-common.c: In function
>'lto_file_decl_data* lto_file_read(lto_file*, std::FILE*, int*)':
>/vol/gcc/src/hg/trunk/local/gcc/lto/lt
On May 6, 2019 3:22:42 PM GMT+02:00, Jakub Jelinek wrote:
>Hi!
>
>The following patch adds some store-merging improvements.
>Previously, only stores where the lhs was
>ARRAY_REF, ARRAY_RANGE_REF, MEM_REF, COMPONENT_REF or BIT_FIELD_REF
>were considered, as the testcases show it is useful to consid
Unfortunately, this patch was still in the making at the release of
9.1. It is more or less self explanatory with the ChangeLogs.
It should be noted that gfc_conv_expr_present could not be used in the
fix for PR90093 because the passed descriptor is a CFI type. Instead,
the test is for a null poin
It helps to attach the patch!
On Mon, 6 May 2019 at 19:57, Paul Richard Thomas
wrote:
>
> Unfortunately, this patch was still in the making at the release of
> 9.1. It is more or less self explanatory with the ChangeLogs.
>
> It should be noted that gfc_conv_expr_present could not be used in the
On Fri, May 3, 2019 at 3:11 PM Maciej W. Rozycki wrote:
> Hmm, I've been thinking a little bit about this hybrid mode and I have
> one question: how do we pass the IEEE rounding mode setting between `fcsr'
> and softfp where we have `-march=rv32imafc -mabi=ilp32' and
> `-march=rv32imac -mabi=ilp3
On 3 May 2019 18:48:09 CEST, "H.J. Lu" wrote:
>On Fri, May 3, 2019 at 6:02 AM Richard Biener
>wrote:
>>
>>
>> The following refactors simplify_vector_constructor and adds
>> handling of constants to it in a straight-forward way.
>>
>> A followup will handle the testcases posted in HJs patch.
>>
>
On Mon, May 06, 2019 at 08:46:05PM +0200, Richard Biener wrote:
> >Fixed as follows. i386-pc-solaris2.11 bootstrap has completed with
> >this
> >patch, sparc-sun-solaris2.11 is running the testsuite and
> >x86_64-pc-linux-gnu is building the runtime libs.
> >
> >Ok for mainline?
>
> Can you use t
On 06/05/19 19:36 +0200, François Dumont wrote:
Hi
This is another attempt to make adapter iterator types operators
undefined when underlying iterator type doesn't support it. For the
move_iterator it is rather easy and even already done for the
operator- so I just generalize it to compar
-Wsuggest-override warns for virtual functions that could use the override
keyword. But as everyone in this PR agrees, the warning shouldn't suggest
adding "override" for "final" functions. This trivial patch implements that.
Bootstrapped/regtested on x86_64-linux, ok for trunk/9?
2019-05-06 M
We don't need this.
Segher
2019-05-06 Segher Boessenkool
* config/rs6000/rs6000.h (PRE_GCC3_DWARF_FRAME_REGISTERS): Delete.
---
gcc/config/rs6000/rs6000.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/gcc/config/rs6000/rs6000.h b/gcc/config/rs6000/rs6000.h
index ff9449c..3
The frame pointer and the argument pointer aren't real registers. MQ
was a register on old POWER. All three are still used as arguments to
rs6000_dbx_register_number during initialisation. If we handle them
explicitly we can do a gcc_unreachable to catch other unexpected
registers.
Tested on po
We do not need to expose the TM registers in debug info. It isn't
actually useful there, because none of the theing that can modify
these register (other than explicit moves) are marked.
We also do not need the registers for GCC itself internally. This
patch deletes them.
Tested on powerpc64-li
Ping.
On Wed, May 01, 2019 at 11:06:08PM -0700, Steve Kargl wrote:
> The attach patch adds a check that a module prefix
> occurs only in a module, submodule, or interface.
>
> C1547 (R1526) MODULE shall appear only in the function-stmt or
>subroutine-stmt of a module subprogram or of a nonab
On Thu, May 02, 2019 at 09:19:10AM +0300, Janne Blomqvist wrote:
> On Thu, May 2, 2019 at 9:02 AM Steve Kargl
> wrote:
> >
> > The attach patch adds an additional check for the
> > STOP code when -std=f2008 is used. The patch has
> > been bootstrapped and regression tested on
> > x86_64-*-freebsd
This renumbers the registers.
It moves the VRs to 64..95, right after the GPRs and the FPRS. This
means that the VSRs (which are aliases to the FPRs and the VRs, in
that order) are consecutive now.
It removes MQ, which has been just a stub for ages (it is a leftover
from RIOS, old POWER).
It mo
Since GCC 9.1 released [2019-05-03].
I'll merge this to trunk?
On Wed, Apr 17, 2019 at 7:14 PM Uros Bizjak wrote:
>
> On Wed, Apr 17, 2019 at 1:03 PM Uros Bizjak wrote:
> >
> > On Wed, Apr 17, 2019 at 12:29 PM Hongtao Liu wrote:
> > >
> > > On Fri, Apr 12, 2019 at 11:18 PM H.J. Lu wrote:
>
在 2019/5/6 下午7:58, JunMa 写道:
在 2019/5/6 下午6:02, Richard Biener 写道:
On Thu, Mar 21, 2019 at 5:57 AM JunMa wrote:
Hi
For now, gcc can not fold code like:
const char a[5] = "123"
__builtin_memchr (a, '7', sizeof a)
It tries to avoid folding out of string length although length of a
is 5.
This
在 2019/5/7 上午2:05, Martin Sebor 写道:
On 5/6/19 5:58 AM, JunMa wrote:
在 2019/5/6 下午6:02, Richard Biener 写道:
On Thu, Mar 21, 2019 at 5:57 AM JunMa wrote:
Hi
For now, gcc can not fold code like:
const char a[5] = "123"
__builtin_memchr (a, '7', sizeof a)
It tries to avoid folding out of string
Hi
I just prefer to make the tests implementation-agnostic using reserve.
I check that without the patch to initiate the hashtable with 11
buckets I reproduce the failures and that with this patch it is fine.
PR libstdc++/90277
* testsuite/23_containers/unordered_multiset/inse
Hi Uros and GCC:
This patch is to fix ix86_expand_sse_comi_round whose implementation
was not correct.
New implentation aligns with _mm_cmp_round_s[sd]_mask.
Bootstrap and regression tests for x86 is fine.
Ok for trunk?
ChangeLog:
gcc/
* config/i386/i386-expand.c (ix86_expand_sse_comi_rou
On Wed, Apr 17, 2019 at 7:14 PM Uros Bizjak wrote:
>
> On Wed, Apr 17, 2019 at 1:03 PM Uros Bizjak wrote:
> >
> > On Wed, Apr 17, 2019 at 12:29 PM Hongtao Liu wrote:
> > >
> > > On Fri, Apr 12, 2019 at 11:18 PM H.J. Lu wrote:
> > > >
> > > > On Fri, Apr 12, 2019 at 3:19 AM Uros Bizjak wrote:
>
83 matches
Mail list logo
