On Tue, 9 Jan 2018, Jeff Law wrote:
> On 01/05/2018 02:01 AM, Richard Biener wrote:
> > On Tue, 28 Nov 2017, Richard Biener wrote:
> >
> >>
> >> The following adds a new target hook, targetm.vectorize.split_reduction,
> >> which allows the target to specify a preferred mode to perform the
> >> fi
Hi,
this patch makes ICE in the testcase in PR83575 go away, it however is not
complete
fix. The problem there is that bb-reorder messes up block partitioning when
profile
is insane and we ICE on multiple hot-cold partition transitions.
This patch fixes the origin of insane profile that is caus
This joint work rewrites LTO debug section copying to not leave
discarded sections around as SHT_NULL but to really discard them
and deal with the fallout (remapping all remaining section references).
This is to avoid diagnostics from the Solaris linker which doesn't
like those.
LTO bootstrapped
> It's really just a couple of new primitives to emit a jump as a call and
> one to slam in a new return address. Given those I think you can do the
> entire implementation as RTL at expansion time and you've got a damn
> good shot at protecting most architectures from these kinds of attacks.
I t
Hi Jeff
On 09/01/18 23:43, Jeff Law wrote:
On 01/05/2018 12:25 PM, Sudakshina Das wrote:
Hi Jeff
On 05/01/18 18:44, Jeff Law wrote:
On 01/04/2018 08:35 AM, Sudakshina Das wrote:
Hi
The bug reported a particular test di-longlong64-sync-1.c failing when
run on arm-linux-gnueabi with options -
The following fixes LTO bootstrap with Ada enabled which currently
fails in the attribute duplicate sanity checking I added last year.
The reason is we end up with a BLOCK_NONLOCALIZED_VARS function decl
inlined somewhere (thus has received a self-origin from dwarf2out)
and referenced in a functi
Hi Kyrill,
On 8 January 2018 at 18:55, Kyrill Tkachov wrote:
> [resending due to mailer problems...]
>
> Hi all,
>
> This patch adds support for the Armv8.4-A architecture [1]
> in the arm backend. This is done through the new
> -march=armv8.4-a option.
>
> With this patch armv8.4-a is recognis
Hi,
What do you think about changing these types to UHI_FTYPE_V16QI_V16QI_UHI and
so on?
In docs it is (KL, VL) = (16,128), (32,256), (64, 512) - so looks like this is
where the error was from the start.
Here is the patch.
Thanks,
Julia
> -Original Message-
> From: Koval, Julia
> Sent:
Hi Christophe,
On 10/01/18 10:50, Christophe Lyon wrote:
Hi Kyrill,
On 8 January 2018 at 18:55, Kyrill Tkachov wrote:
[resending due to mailer problems...]
Hi all,
This patch adds support for the Armv8.4-A architecture [1]
in the arm backend. This is done through the new
-march=armv8.4-a
Need to convert the RHS to the type of the LHS when assigning.
Regtested on x86_64-pc-linux-gnu, committed as obvious.
gcc/fortran/ChangeLog:
2018-01-10 Janne Blomqvist
PR fortran/84740
* trans-array.c (gfc_trans_array_ctor_element): Convert RHS to the
LHS type when a
Hi Richard,
> This joint work rewrites LTO debug section copying to not leave
> discarded sections around as SHT_NULL but to really discard them
> and deal with the fallout (remapping all remaining section references).
> This is to avoid diagnostics from the Solaris linker which doesn't
> like tho
On Wed, Jan 10, 2018 at 01:18:46PM +0200, Janne Blomqvist wrote:
Thanks for fixing this PR.
> @@ -1562,7 +1562,8 @@ gfc_trans_array_ctor_element (stmtblock_t * pblock,
> tree desc,
> if (first_len)
> {
> gfc_add_modify (&se->pre, first_len_val,
> -
Hi,
this is the secodn half of fix for PR83575 which avoids ICE in the quite rare
scenarios bb-reorder produces fixable partition but we can't fix it because
bb order is already fixed :)
This is done by skipping verification during this transition and enforcing this
missed optimization check only w
On Wed, Jan 10, 2018 at 1:21 PM, Jakub Jelinek wrote:
> On Wed, Jan 10, 2018 at 01:18:46PM +0200, Janne Blomqvist wrote:
>
> Thanks for fixing this PR.
>
>> @@ -1562,7 +1562,8 @@ gfc_trans_array_ctor_element (stmtblock_t * pblock,
>> tree desc,
>> if (first_len)
>> {
>>
Hi Ian,
>> the patch broke Solaris bootstrap:
>>
>> mv: cannot stat 'os/signal/internal/pty.s-gox.tmp': No such file or directory
>> make[4]: *** [Makefile:3348: os/signal/internal/pty.s-gox] Error 1
>> make[4]: *** Waiting for unfinished jobs
>>
>> Fixed trivially as follows, which allowed th
Hi!
In libcpp, we have quite a lot of state on the token flags, some
related to the stuff that comes before the token (e.g.
PREV_FALLTHROUGH, PREV_WHITE and STRINGIFY_ARG), others related to the
stuff that comes after the token (e.g. PASTE_LEFT, SP_DIGRAPH, SP_PREV_WHITE).
Unfortunately, with the
On Wed, Jan 10, 2018 at 2:18 AM, Eric Botcazou wrote:
>> It's really just a couple of new primitives to emit a jump as a call and
>> one to slam in a new return address. Given those I think you can do the
>> entire implementation as RTL at expansion time and you've got a damn
>> good shot at prot
On 10 January 2018 at 12:05, Kyrill Tkachov
wrote:
> Hi Christophe,
>
>
> On 10/01/18 10:50, Christophe Lyon wrote:
>>
>> Hi Kyrill,
>>
>>
>> On 8 January 2018 at 18:55, Kyrill Tkachov
>> wrote:
>>>
>>> [resending due to mailer problems...]
>>>
>>> Hi all,
>>>
>>> This patch adds support for th
On Tue, Jan 9, 2018 at 10:59 PM, Richard Sandiford
wrote:
> After cunrolling the inner loop, the remaining loop in the testcase
> has a single 32-bit access and a group of 64-bit accesses. We first
> try to vectorise at 128 bits (VF 4), but decide not to for cost reasons.
> We then try with 64 bi
On Wed, Jan 10, 2018 at 11:18 AM, Eric Botcazou wrote:
>> It's really just a couple of new primitives to emit a jump as a call and
>> one to slam in a new return address. Given those I think you can do the
>> entire implementation as RTL at expansion time and you've got a damn
>> good shot at pro
On Tue, Jan 9, 2018 at 4:36 PM, Richard Sandiford
wrote:
> Ping
Ok.
Richard.
> Richard Sandiford writes:
>> Richard Biener writes:
>>> On Mon, Nov 20, 2017 at 1:54 PM, Richard Sandiford
>>> wrote:
Richard Biener writes:
> On Fri, Nov 17, 2017 at 5:53 PM, Richard Sandiford
> wr
On Tue, Jan 9, 2018 at 7:29 PM, Jeff Law wrote:
> On 01/09/2018 07:43 AM, Martin Liška wrote:
>> On 09/20/2017 05:00 PM, Jeff Law wrote:
>>> On 09/20/2017 01:24 AM, Martin Liška wrote:
>>>
Hello.
Thank you Jeff for very verbose explanation what's happening. I'm planning
t
On Wed, Jan 10, 2018 at 02:08:48PM +0100, Richard Biener wrote:
> On Wed, Jan 10, 2018 at 11:18 AM, Eric Botcazou wrote:
> >> It's really just a couple of new primitives to emit a jump as a call and
> >> one to slam in a new return address. Given those I think you can do the
> >> entire implement
On Tue, Jan 9, 2018 at 11:34 PM, Uros Bizjak wrote:
>> This patch updates libgo to the Go1.10beta1 release. The final Go
>> 1.10 release is expected around February 1, so it's not clear how the
>> release timing is going to work with GCC 8. In any case this updates
>> GCC to something pretty clo
Hi Janne,
With this patch, bootstrap fails with
../../work/gcc/fortran/array.c: In function 'bool
gfc_resolve_character_array_constructor(gfc_expr*)':
../../work/gcc/fortran/array.c:2062:36: error: unknown conversion type
character 'l' in format [-Werror=format=]
current_length, &p->expr->
On Wed, Jan 10, 2018 at 5:35 AM, Ian Lance Taylor wrote:
> On Tue, Jan 9, 2018 at 11:34 PM, Uros Bizjak wrote:
>>> This patch updates libgo to the Go1.10beta1 release. The final Go
>>> 1.10 release is expected around February 1, so it's not clear how the
>>> release timing is going to work with
On Wed, Jan 10, 2018 at 3:44 AM, Rainer Orth
wrote:
>
>>> the patch broke Solaris bootstrap:
>>>
>>> mv: cannot stat 'os/signal/internal/pty.s-gox.tmp': No such file or
>>> directory
>>> make[4]: *** [Makefile:3348: os/signal/internal/pty.s-gox] Error 1
>>> make[4]: *** Waiting for unfinished job
On Wed, Jan 10, 2018 at 5:14 AM, Jakub Jelinek wrote:
> On Wed, Jan 10, 2018 at 02:08:48PM +0100, Richard Biener wrote:
>> On Wed, Jan 10, 2018 at 11:18 AM, Eric Botcazou
>> wrote:
>> >> It's really just a couple of new primitives to emit a jump as a call and
>> >> one to slam in a new return ad
On Mon, Nov 06, 2017 at 01:50:07PM +, Wilco Dijkstra wrote:
> Richard Sandiford wrote:
> >
> > Yeah, I'd hit this too. I think it's a latent bug that just
> > happened to be exposed by Wilco's patch: although the *movti_aarch64
> > predicate disallows const_wide_int, the constraints allow it v
On Wed, Jan 10, 2018 at 2:37 PM, Ian Lance Taylor wrote:
> On Wed, Jan 10, 2018 at 5:35 AM, Ian Lance Taylor wrote:
>> On Tue, Jan 9, 2018 at 11:34 PM, Uros Bizjak wrote:
This patch updates libgo to the Go1.10beta1 release. The final Go
1.10 release is expected around February 1, so i
On Sun, Dec 17, 2017 at 4:38 AM, John Paul Adrian Glaubitz
wrote:
>
> This is the second version of my patch to add support for SuperH
> in libgo. The changes over my first patch in [1] are:
>
> * account for little- and big-endian targets
> * account for sh3- and sh4-specific parameters
>
> I h
On 08/01/18 19:37, Aaron Sawdey wrote:
> On Tue, 2017-12-12 at 10:13 -0600, Segher Boessenkool wrote:
>> > Please fix those trivialities, and it's okay for trunk (after the
>> > rtlanal patch is approved too). Thanks!
> Here's the final version of this, which is committed as 256351.
>
>
> 2018-0
On 01/10/2018 03:25 PM, Ian Lance Taylor wrote:
Thanks. I finally took a look at this. I don't know much about SH,
but I don't think we want to add each SH variant as a separate GOARCH
value. As you can see from the list you modified in
ibgo/go/go/build/syslist.go, the difference between GOARC
On Wed, Jan 10, 2018 at 6:00 AM, Uros Bizjak wrote:
> On Wed, Jan 10, 2018 at 2:37 PM, Ian Lance Taylor wrote:
>> On Wed, Jan 10, 2018 at 5:35 AM, Ian Lance Taylor wrote:
>>> On Tue, Jan 9, 2018 at 11:34 PM, Uros Bizjak wrote:
> This patch updates libgo to the Go1.10beta1 release. The fina
On Wed, 2018-01-10 at 06:25 -0800, Ian Lance Taylor wrote:
>
> Thanks. I finally took a look at this. I don't know much about SH,
> but I don't think we want to add each SH variant as a separate GOARCH
> value. As you can see from the list you modified in
> ibgo/go/go/build/syslist.go, the diff
On Wed, Jan 10, 2018 at 6:30 AM, John Paul Adrian Glaubitz
wrote:
> On 01/10/2018 03:25 PM, Ian Lance Taylor wrote:
>>
>> Thanks. I finally took a look at this. I don't know much about SH,
>> but I don't think we want to add each SH variant as a separate GOARCH
>> value. As you can see from the
Tested on x86_64-unknown-linux-gnu, applied.
Richard.
2018-01-10 Richard Biener
PR debug/82425
* gcc.dg/guality/inline-params-2.c: Un-XFAIL for slim LTO.
Index: gcc/testsuite/gcc.dg/guality/inline-params-2.c
===
On Mon, Oct 23, 2017 at 02:30:24PM +0200, Christophe Lyon wrote:
> After Jakub's suggestion in PR82120 and PR81184, the attached patch
> adds the -mbranch-cost option to the ARM target. My understanding
> is that it's intended to be used internally for testing and does not
> require user-facing doc
On 01/10/2018 03:40 PM, Ian Lance Taylor wrote:
The main purpose of a GOARCH value is to specify build targets, which
are the +build lines seen in files like
libgo/go/internal/syscall/unix/getrandom_linux_mipsx.go. They also
appear in file names. It seems to me unlikely that it will ever be
nec
This patch adds a bit more the the avr section of the v8 release notes.
Ok?
Johann
Index: changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-8/changes.html,v
retrieving revision 1.25
diff -r1.25 changes.html
240a241,246
>
>
On Wed, Jan 10, 2018 at 6:30 AM, Oleg Endo wrote:
> On Wed, 2018-01-10 at 06:25 -0800, Ian Lance Taylor wrote:
>>
>> Thanks. I finally took a look at this. I don't know much about SH,
>> but I don't think we want to add each SH variant as a separate GOARCH
>> value. As you can see from the list
Applied.
Richard.
2018-01-10 Richard Biener
PR testsuite/78768
* gcc.dg/pr78768.c: Un-XFAIL.
Index: gcc/testsuite/gcc.dg/pr78768.c
===
--- gcc/testsuite/gcc.dg/pr78768.c (revision 256428)
+++ gcc/testsuite/
In various of our 32-bit load_toc patterns we take the difference of
two immediates (labels) as a term to something bigger; but this isn't
canonical RTL, it needs to be wrapped in CONST.
This fixes it. Tested on powerpc64-linux {-m32,-m64}. Committing.
Segher
2018-01-10 Segher Boessenkool
On Wed, Jan 10, 2018 at 3:44 AM, Rainer Orth
wrote:
>
> thanks. Testing has now concluded as well. x86 results are good (no
> regressions except for cmd/internal/buildid which fails on Linux, too),
> as are 64-bit sparc results.
The cmd/internal/buildid test does pass on my system. What are yo
On 01/10/2018 02:13 PM, Richard Biener wrote:
> On Tue, Jan 9, 2018 at 7:29 PM, Jeff Law wrote:
>> On 01/09/2018 07:43 AM, Martin Liška wrote:
>>> On 09/20/2017 05:00 PM, Jeff Law wrote:
On 09/20/2017 01:24 AM, Martin Liška wrote:
>
> Hello.
>
> Thank you Jeff for very ve
On Wed, Jan 10, 2018 at 5:42 AM, Ian Lance Taylor wrote:
>
> Whoops, there's a bug on big-endian 32-bit systems. I'm testing
> https://golang.org/cl/87135.
Committed as follows.
Ian
Index: gcc/go/gofrontend/MERGE
===
--- gcc/go/gof
On 01/10/2018 03:51 PM, Ian Lance Taylor wrote:
I suppose I shouldn't have said calling convention, as that cuts too
finely. There are similar issues with MIPS and even x86 has softfloat
variants. Those options are selectable via command line options in
GCC, and in the gc toolchain they are sel
OK.
On Thu, Dec 21, 2017 at 2:21 PM, Paolo Carlini wrote:
> Hi,
>
> On 21/12/2017 17:04, Jason Merrill wrote:
>>
>> On Wed, Dec 20, 2017 at 10:37 AM, Paolo Carlini
>> wrote:
>>>
>>> in this error recovery regression, after a sensible error produced by
>>> unqualified_name_lookup_error we ICE muc
On 10 January 2018 at 15:44, Jakub Jelinek wrote:
> On Mon, Oct 23, 2017 at 02:30:24PM +0200, Christophe Lyon wrote:
>> After Jakub's suggestion in PR82120 and PR81184, the attached patch
>> adds the -mbranch-cost option to the ARM target. My understanding
>> is that it's intended to be used inter
On Wed, Jan 10, 2018 at 6:34 AM, Ian Lance Taylor wrote:
>
> Thanks. I think https://golang.org/cl/87137 will fix it.
Committed as follows.
Ian
Index: gcc/go/gofrontend/MERGE
===
--- gcc/go/gofrontend/MERGE (revision 256431)
++
On Fri, Jun 09, 2017 at 03:46:41PM -0700, Jason Merrill wrote:
> Something that was missed previously in the delayed folding work:
> there's no good reason to be pulling values out of constants in
> convert_like_real.
Well, it breaks nontype10.C on 32-bit targets.
Or, let's use a modified version
I'll check the runtime of that --- I added some test cases to memcmp-
1.c and probably it is now taking too long. I will revise it so it's no
longer than it was before.
Aaron
On Wed, 2018-01-10 at 14:25 +, Szabolcs Nagy wrote:
> On 08/01/18 19:37, Aaron Sawdey wrote:
> > On Tue, 2017-12-12
On Wed, Jan 10, 2018 at 7:05 AM, John Paul Adrian Glaubitz
wrote:
> On 01/10/2018 03:51 PM, Ian Lance Taylor wrote:
>>
>> I suppose I shouldn't have said calling convention, as that cuts too
>> finely. There are similar issues with MIPS and even x86 has softfloat
>> variants. Those options are s
On Fri, Dec 22, 2017 at 7:34 PM, Paolo Carlini wrote:
> in this error recovery issue cp_check_const_attributes and more generally
> cplus_decl_attributes have lots of troubles handling the error_mark_node
> returned by cp_parser_std_attribute_spec_seq, as called by
> cp_parser_direct_declarator. I
This libgo patch removes the exp/proxy and exp/terminal packages.
The exp/proxy package was removed from the master library in
https://golang.org/cl/6461056 (August, 2012).
The exp/terminal package was removed from the master library in
https://golang.org/cl/5970044 (March, 2012).
I'm not sure w
On 01/10/2018 04:22 PM, Ian Lance Taylor wrote:
Ok, so basically we should end up having only two GOARCHes for SH,
being "sh" and "shbe", correct?
Yes, I would like to start there.
If, yes, I can rebase my patch, make the requested changes and resubmit
it to Gerrit.
Thanks!
Done: https://g
On Thu, Jan 4, 2018 at 6:53 PM, Martin Sebor wrote:
>
> PR 82922 asks to enable -Wstrict-prototypes. The attached
> patch handles the errors in an x86_64 bootstrap. With it,
> GCC bootstraps successfully with --enable-languages=all,jit,
> but there are many FAILs in the test suite but I think th
Hi Ian,
> On Wed, Jan 10, 2018 at 3:44 AM, Rainer Orth
> wrote:
>>
>> thanks. Testing has now concluded as well. x86 results are good (no
>> regressions except for cmd/internal/buildid which fails on Linux, too),
>> as are 64-bit sparc results.
>
> The cmd/internal/buildid test does pass on my
On Fri, Jan 5, 2018 at 6:37 PM, Martin Sebor wrote:
> On 01/05/2018 03:02 PM, Jakub Jelinek wrote:
>>
>> Hi!
>>
>> Apparently LLVM allows similar warning to -Wclass-memaccess (is it just
>> similar or same?; if the latter, perhaps we should use the same option for
>> that) to be disabled not just
Hi Jeff
On 10/01/18 10:44, Sudakshina Das wrote:
Hi Jeff
On 09/01/18 23:43, Jeff Law wrote:
On 01/05/2018 12:25 PM, Sudakshina Das wrote:
Hi Jeff
On 05/01/18 18:44, Jeff Law wrote:
On 01/04/2018 08:35 AM, Sudakshina Das wrote:
Hi
The bug reported a particular test di-longlong64-sync-1.c f
On Wed, Jan 10, 2018 at 10:46:06AM -0500, Jason Merrill wrote:
> >> This patch moves the warning tiny bit earlier (from build_cxx_call to the
> >> caller) where we still have information about the original parsed
> >> arguments before conversions to the builtin argument types.
>
> OK.
Is that an
Hi,
On 10/01/2018 16:32, Jason Merrill wrote:
On Fri, Dec 22, 2017 at 7:34 PM, Paolo Carlini wrote:
in this error recovery issue cp_check_const_attributes and more generally
cplus_decl_attributes have lots of troubles handling the error_mark_node
returned by cp_parser_std_attribute_spec_seq, a
On Fri, Jan 5, 2018 at 5:14 PM, Jakub Jelinek wrote:
> Jason's recent change removed a mark_rvalue_use call from constant_value_1,
> which unfortunately regressed quite a few cases where
> -Wunused-but-set-variable now has false positives.
> The easiest fix seems to be just deal with the -Wunused
OK.
On Tue, Jan 2, 2018 at 9:51 AM, Marek Polacek wrote:
> This PR complains about a bogus -Wduplicated-branches warning with a non-type
> template argument. That can be easily fixed with a new sentinel. I also
> noticed a missing tf_warning warning check, so I added it for good measure.
>
> Bo
On Wed, Jan 10, 2018 at 11:52:16AM -0500, Jason Merrill wrote:
> On Fri, Jan 5, 2018 at 5:14 PM, Jakub Jelinek wrote:
> > Jason's recent change removed a mark_rvalue_use call from constant_value_1,
> > which unfortunately regressed quite a few cases where
> > -Wunused-but-set-variable now has fals
On Wed, Jan 10, 2018 at 11:25 AM, Jakub Jelinek wrote:
> On Wed, Jan 10, 2018 at 10:46:06AM -0500, Jason Merrill wrote:
>> >> This patch moves the warning tiny bit earlier (from build_cxx_call to the
>> >> caller) where we still have information about the original parsed
>> >> arguments before con
On Wed, Jan 10, 2018 at 11:33 AM, Paolo Carlini
wrote:
> Hi,
>
> On 10/01/2018 16:32, Jason Merrill wrote:
>>
>> On Fri, Dec 22, 2017 at 7:34 PM, Paolo Carlini
>> wrote:
>>>
>>> in this error recovery issue cp_check_const_attributes and more generally
>>> cplus_decl_attributes have lots of troubl
On Wed, Jan 10, 2018 at 11:56 AM, Jakub Jelinek wrote:
> On Wed, Jan 10, 2018 at 11:52:16AM -0500, Jason Merrill wrote:
>> On Fri, Jan 5, 2018 at 5:14 PM, Jakub Jelinek wrote:
>> > Jason's recent change removed a mark_rvalue_use call from constant_value_1,
>> > which unfortunately regressed quite
On 01/10/2018 03:05 AM, Richard Biener wrote:
>
> This joint work rewrites LTO debug section copying to not leave
> discarded sections around as SHT_NULL but to really discard them
> and deal with the fallout (remapping all remaining section references).
> This is to avoid diagnostics from the Sol
This brings it back not quite to where it was but a lot more reasonable
than what I put into 256351.
2018-01-10 Aaron Sawdey
* gcc.dg/memcmp-1.c: Reduce runtime to something reasonable.
OK for trunk?
Thanks,
Aaron
--
Aaron Sawdey, Ph.D. acsaw...@linux.vnet.ibm.com
050-2/C113
>> @@ -671,11 +668,9 @@ convert_control_dep_chain_into_preds (vec
>> *dep_chains,
>> e = one_cd_chain[j];
>> guard_bb = e->src;
>> gsi = gsi_last_bb (guard_bb);
>> + /* Ignore empty BBs as they're basically forwarder blocks. */
>> if (gsi_end_p (gsi))
>> -
On Wed, Jan 10, 2018 at 7:43 AM, Rainer Orth
wrote:
> Hi Ian,
>
>> On Wed, Jan 10, 2018 at 3:44 AM, Rainer Orth
>> wrote:
>>>
>>> thanks. Testing has now concluded as well. x86 results are good (no
>>> regressions except for cmd/internal/buildid which fails on Linux, too),
>>> as are 64-bit spa
On January 10, 2018 6:28:57 PM GMT+01:00, Jeff Law wrote:
>On 01/10/2018 03:05 AM, Richard Biener wrote:
>>
>> This joint work rewrites LTO debug section copying to not leave
>> discarded sections around as SHT_NULL but to really discard them
>> and deal with the fallout (remapping all remaining
On 01/10/2018 10:46 AM, Aaron Sawdey wrote:
> This brings it back not quite to where it was but a lot more reasonable
> than what I put into 256351.
>
> 2018-01-10 Aaron Sawdey
>
> * gcc.dg/memcmp-1.c: Reduce runtime to something reasonable.
>
> OK for trunk?
>
> Thanks,
>Aaron
>
On 01/10/2018 07:48 AM, Georg-Johann Lay wrote:
> This patch adds a bit more the the avr section of the v8 release notes.
>
> Ok?
OK.
jeff
On Tue, Jan 09, 2018 at 09:13:23PM -0800, Andrew Pinski wrote:
> On Tue, Jan 9, 2018 at 6:54 AM, Segher Boessenkool
> wrote:
> > On Tue, Jan 09, 2018 at 12:23:42PM +, Wilco Dijkstra wrote:
> >> Segher Boessenkool wrote:
> >> > On Mon, Jan 08, 2018 at 0:25:47PM +, Wilco Dijkstra wrote:
> >>
Hi,
I have attached patch for PR81703 rebased on Martin's fix for PR83501
posted here since both had considerable overlaps:
https://gcc.gnu.org/ml/gcc-patches/2018-01/msg00180.html
The patch passes bootstrap+test on x86_64-unknown-linux-gnu
and cross-tested on aarch64-*-*.
Currently it fails to pa
Hello,
I would really like to ping the FMA transformation prevention patch that
I sent here in December, which, after incorporating a suggestion from
Richi, re-base and re-testing, I re-post below. I really think that it
should make into gcc 8 in some form, because the performance wins are
really
Hi,
The attached patch tries to fix PR83775.
Validation in progress.
OK to commit if passes ?
Thanks,
Prathamesh
2018-01-11 Prathamesh Kulkarni
PR target/83775
* config/arm/arm.c (arm_declare_function_name): Set arch_to_print if
targ_options->x_arm_arch_string is non NU
On 01/10/2018 11:46 AM, Martin Jambor wrote:
> Hello,
>
> I would really like to ping the FMA transformation prevention patch that
> I sent here in December, which, after incorporating a suggestion from
> Richi, re-base and re-testing, I re-post below. I really think that it
> should make into gc
On Fri, Jan 05, 2018 at 11:41:25AM +, Richard Sandiford wrote:
> Here's the patch updated to apply on top of the v8.4 and
> __builtin_load_no_speculate support. It also handles the new
> vec_perm_indices and CONST_VECTOR encoding and uses VNx... names
> for the SVE modes.
>
> Richard Sandifor
This libgo patch by John Paul Adrian Glaubitz adds SH support to
libgo. Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu,
which I admit doesn't prove much. Committed to mainline.
Ian
Index: gcc/go/gofrontend/MERGE
===
--- gc
On Tue, Jan 09, 2018 at 06:28:09PM +, Michael Collison wrote:
> Patch updated per Richard's comments. Ok for trunk?
This patch adds a lot of code, much of which looks like it ought to be
possible to common up using the iterators. I'm going to OK it as is, as I'd
like to see this make GCC 8, an
On 01/10/2018 12:01 PM, Prathamesh Kulkarni wrote:
Hi,
The attached patch tries to fix PR83775.
Validation in progress.
OK to commit if passes ?
FWIW, the patch makes sense to me as it simplifies things for
me when debugging using a cross-compiler. I reported the same
ICE in bug 83775 and it w
Joseph,
On Sat, Jan 06, 2018 at 08:45:33AM +0100, Richard Biener wrote:
> On January 5, 2018 10:13:34 PM GMT+01:00, Joseph Myers
> wrote:
> >unrelated. OK to commit?
>
> OK.
>
> Richard.
> >Index: gcc/match.pd
> >===
> >--- g
On 01/06/2018 03:04 PM, Martin Sebor wrote:
> Bug 83671 - Fix for false positive reported by -Wstringop-overflow
> does not work at -O1, points out that the string length range
> optimization implemented as a solution for bug 83373 doesn't help
> at -O1. The root cause is that the fix was added to
On Tue, Jan 09, 2018 at 12:22:38PM -0600, Peter Bergner wrote:
> PR83399 shows a problem where we emit an altivec load using a builtin
> that forces us to use a specific altivec load pattern. The generated
> rtl pattern has a use of sfp (frame pointer) and during LRA, we eliminate
> it's use to th
All of the various parts of this kit have now been approved; I've
committed it to trunk as r256448.
(The initial version of the kit was posted 2017-10-20, and
the followup on 2017-11-10, both in stage 1; the final patch
approval was 2018-01-09, towards the end of stage 3).
Successfully bootstrapp
The AIX stat function apparently uses an _st_timespec type. This
libgo patch by Tony Reix handles that correctly. Bootstrapped on
x86_64-pc-linux-gnu. Committed to mainline.
Ian
Index: gcc/go/gofrontend/MERGE
===
--- gcc/go/gofront
Thanks for the review!
James Greenhalgh writes:
> On Fri, Jan 05, 2018 at 11:41:25AM +, Richard Sandiford wrote:
>> Here's the patch updated to apply on top of the v8.4 and
>> __builtin_load_no_speculate support. It also handles the new
>> vec_perm_indices and CONST_VECTOR encoding and uses
On 1/10/18 1:44 PM, Segher Boessenkool wrote:
> On Tue, Jan 09, 2018 at 12:22:38PM -0600, Peter Bergner wrote:
>> * config/rs6000/rs6000.c (print_operand): Use
>> VECTOR_MEM_ALTIVEC_OR_VSX_P.
>
> (print_operand) <'y'>: ...
Will fix.
>> * config/rs6000/vsx.md (*vsx_le_perm_load_)
Hi,
On 10/01/2018 17:58, Jason Merrill wrote:
On Wed, Jan 10, 2018 at 11:33 AM, Paolo Carlini
wrote:
Hi,
On 10/01/2018 16:32, Jason Merrill wrote:
On Fri, Dec 22, 2017 at 7:34 PM, Paolo Carlini
wrote:
in this error recovery issue cp_check_const_attributes and more generally
cplus_decl_attr
On Tue, Jan 09, 2018 at 04:09:25PM -0600, Peter Bergner wrote:
> The following patch changes the x86 intrinsic compat headers to use #error
> instead of #warning. We do this for two reasons. Firstly, we want the user
> to really be sure they want/need to use the x86 intrinsic compat support
> bef
On Wed, 10 Jan 2018, Bernhard Reutner-Fischer wrote:
> > >+ /* x <= +Inf is the same as x == x, i.e. !isnan(x), but this loses
> > >+ an "invalid" exception. */
> > >+ (if (!flag_trapping_math)
> > >+ (eq @0 @0
> > >+ /* x == +Inf and x >= +Inf are always equal to x > DBL_MAX, bu
As I add support for making -mabi=ieeelongdouble default, I noticed some issues
in building libstdc++ with the default for the code that supports the
-mlong-double-64 option. These tests add checks for -mlong-double-128 before
considering whether TFmode/TCmode are IEEE or IBM extended double.
I w
On 1/10/18 2:14 PM, Segher Boessenkool wrote:
> On Tue, Jan 09, 2018 at 04:09:25PM -0600, Peter Bergner wrote:
>> The following patch changes the x86 intrinsic compat headers to use #error
>> instead of #warning. We do this for two reasons. Firstly, we want the user
>> to really be sure they want
To avoid issuing duplicate warnings for the same function call
in the source code the -Wrestrict warning code makes sure
the no-warning bit is propagated between trees and GIMPLE and
tested before issuing a warning. But the warning also detects
some of the same problems as -Wstringop-overflow, an
Okay will put on my to-do list for post GCC 8.
-Original Message-
From: James Greenhalgh [mailto:james.greenha...@arm.com]
Sent: Wednesday, January 10, 2018 12:21 PM
To: Michael Collison
Cc: Richard Sandiford ; GCC Patches
; nd
Subject: Re: [PATCH 5/5][AArch64] fp16fml support
On Tue,
Hi,
On Wed, Jan 10, 2018 at 01:55:34PM -0600, Peter Bergner wrote:
> >> @@ -570,7 +570,7 @@ (define_split
> >> ;; The post-reload split requires that we re-permute the source
> >> ;; register in case it is still live.
> >> (define_split
> >> - [(set (match_operand:VSX_D 0 "memory_operand" "")
When a function call is removed, it may become a leaf function. But if
argument may be passed on stack, we need to align the stack frame when
there is no tail call.
Tested on Linux/i686 and Linux/x86-64.
OK for trunk?
H.J.
---
gcc/
PR target/83330
* config/i386/i386.c (ix86_com
1 - 100 of 138 matches
Mail list logo
