On Mon, 22 Oct 2018 at 23:01, Thomas Koenig wrote:
> Anyway, the attached patch fixes this, plus the print *, instead
> of test for return values, plus the whitespace issues mentioned
> by Bernhard. Patch gzipped this time to let it go through to
> gcc-patches.
Thanks, The few remainin issues ar
On 10/18/2018 10:34 PM, Jonathan Wakely wrote:
On 18/10/18 22:12 +0200, François Dumont wrote:
Current build of libstdc++ with
--enable-symvers=gnu-versioned-namespace fails (at least under Linux)
because of:
In file included from
/home/fdt/dev/gcc/build_versioned_ns/x86_64-pc-linux-gnu/libs
Youtube Abone
Artık Herkes Yapıyor Sosyal Hesaplarınızda Beğeni Almak Binlerce Kişi
Tarafından Takip Edilmek Ücretsiz
Merhaba gcc-patches@gcc.gnu.org,
Siz de yakınlarınızın , arkadaşlarınızın yada sosyal hesaplarınızdaki
tanışıklarınızın aşırı beğeni alan içeriklerine ve hergün daha da arta
On 10/01/2018 05:00 PM, Joseph Myers wrote:
On Mon, 1 Oct 2018, Martin Sebor wrote:
Testing the patch with Glibc triggers thousands of warnings of
both kinds. After reviewing a small subset it became apparent
Thousands of warnings suggests initially having the warning outside -Wall
(though o
This patch to the Go frontend changes the export format to index type
data so that it doesn't have to be read until needed. It changes the
importer to only read the exported types at first, and to read other
types as they are needed. It introduces a new "types" command to the
export data to recor
On 10/22/18 7:20 PM, Segher Boessenkool wrote:
> Hi peter,
>> + /* If we have a matching constraint and both operands are hard
>> registers,
>> + then they must be the same hard register. */
>> + if (HARD_REGISTER_P (output)
>> + && HARD_REGISTER_P (input)
>> + && REGNO (o
Ping ?
On Fri, Oct 19, 2018 at 2:19 PM Paul Hua wrote:
>
> Ping?
>
> I'd like check in those patches before stage3.
>
> Thanks,
>
> On Tue, Oct 16, 2018 at 10:49 AM Paul Hua wrote:
> >
> > Hi:
> >
> > The original version of patches were here:
> > https://gcc.gnu.org/ml/gcc-patches/2018-09/msg00
Hi peter,
On Mon, Oct 22, 2018 at 06:40:58PM -0500, Peter Bergner wrote:
> --- gcc/function.c(revision 265399)
> +++ gcc/function.c(working copy)
> @@ -6453,6 +6453,13 @@ match_asm_constraints_1 (rtx_insn *insn,
> || !general_operand (input, GET_MODE (output)))
> continue;
>
Hi!
On Mon, Oct 22, 2018 at 01:33:18PM -0500, Bill Schmidt wrote:
> We should never use __vector long in the intrinsics compatibility headers,
> since this has different meanings on 32- and 64-bit targets. This patch
> corrects a number of places where this previously slipped through.
> --- gcc/
GCC was hitting an ICE on some pdp11 tests due to a typo in a max alignment
check.
Committed as obvious.
paul
ChangeLog:
2018-10-22 Paul Koning
* symtab.c (symtab_node::increase_alignment): Correct max
alignment check.
Index: symtab.c
==
Hi Bill,
On Mon, Oct 22, 2018 at 01:29:15PM -0500, Bill Schmidt wrote:
> The vec_sel intrinsic is overloaded for multiple types. There are a
> couple of cases in our intrinsic compatibility headers where the types
> used don't match any allowable type signature. GCC is able to correctly
> infer
On 10/22/18 6:40 PM, Peter Bergner wrote:
> On 10/22/18 3:58 PM, Jeff Law wrote:
>> On 10/19/18 4:39 PM, Peter Bergner wrote:
>>> Jeff, maybe once Segher commits his patch, can you give this patch a try
>>> on your testers?
>> Once committed to the trunk it's automatically picked up :-) In fact,
>
On 10/22/18 3:58 PM, Jeff Law wrote:
> On 10/19/18 4:39 PM, Peter Bergner wrote:
>> Jeff, maybe once Segher commits his patch, can you give this patch a try
>> on your testers?
> Once committed to the trunk it's automatically picked up :-) In fact,
> commits to the trunk are triggers, though in re
On Mon, Oct 22, 2018 at 01:26:11PM -0500, Paul Clarke wrote:
> Target tests for the intrinsics defined in pmmintrin.h, copied from
> gcc.target/i386.
>
> Tested on POWER8 ppc64le and ppc64 (-m64 and -m32, the latter only reporting
> 16 new unsupported tests), and also by forcing -mcpu=power7 on pp
Hi Paul,
On Mon, Oct 22, 2018 at 01:25:57PM -0500, Paul Clarke wrote:
> This is a follow-on to earlier commits for adding compatibility
> implementations of x86 intrinsics for PPC64LE. This patch adds
> the 32 x86 intrinsics from ("SSSE3").
> +extern __inline __m64 __attribute__((__gnu_inline__
On Mon, 22 Oct 2018, Jason Merrill wrote:
> > I'm thinking of making this feature available as an extension to all of
> > C/C++ perhaps with appropriate pedwarn.
> >
> > Opinions?
>
> That seems reasonable to me, but Joseph will need to weigh in about C.
A C extension would seem reasonable, if
On Mon, 2018-10-22 at 11:15 +0200, Svante Signell wrote:
> Hello,
>
> As advised by the Debian gcc maintainer Matthias Klose and golang
> developer Ian Lance Taylor (Cc:ed) I'm (re-)submitting the patches
> for the port of gccgo to GNU/Hurd.
>
> The 13 patches are:
Due to some editing errors thi
On 10/21/18 4:39 PM, Ed Smith-Rowland wrote:
All,
This patch implements C++2a proposal P0330R2 Literal Suffixes for
ptrdiff_t and size_t*. It's not official yet but looks very likely to
pass. It is incomplete because I'm looking for some opinions. (We also
might wait 'till it actually passe
On 10/13/18 8:19 PM, Martin Sebor wrote:
+ oper = cp_parser_type_id (parser);
+ parser->in_type_id_in_expr_p = saved_in_type_id_in_expr_p;
+
+ if (cp_parser_parse_definitely (parser))
+{
+ /* If all went well, set OPER to the type. */
+ cp_decl_specifier_seq decl_specs;
+
+
On 22 October 2018 19:49:35 CEST, Andrew Burgess
wrote:
>* Claudiu Zissulescu [2018-10-10 11:00:14 +0300]:
>> --- a/gcc/config/arc/arc.c
>> +++ b/gcc/config/arc/arc.c
>> @@ -10803,6 +10803,169 @@ arc_cannot_substitute_mem_equiv_p (rtx)
>>return true;
>> }
>>
>> +/* Checks whether the ope
On 10/19/2018 05:16 PM, Peter Bergner wrote:
Vlad, Jeff and Segher,
I think I have determined what is happening with the aarch64 test case that
is failing after my r264897 commit. It appears my patch is just exposing
an issue in lra-constraints.c:process_alt_operands() when processing an ins
Hi Jeff,
On Mon, Oct 22, 2018 at 02:52:12PM -0600, Jeff Law wrote:
> I know we've gone back and forth on this stuff through the years,
> particularly for targets with likely-to-spilled classes that are used
> for register passing/return values.
Right, there already was code to not copy to a pseud
Hi Dominique,
With your patch, compiling the following test
program logtest3
implicit none
logical :: x = .true.
integer, parameter :: I_FINDLOC_BACK(1) = findloc([1,1],1, &
back=x)
end program logtest3
gives an ICE
I sometimes wonder where you get all these test cases fro
On 10/19/18 4:39 PM, Peter Bergner wrote:
> On 10/19/18 4:16 PM, Peter Bergner wrote:
>> Thoughts? I'll note that this does not fix the S390 bugs, since those seem
>> to be due to problems with early clobber operands and "matching" constraint
>> operands. I'm still working on that and hope to hav
On 10/22/18 2:17 PM, Segher Boessenkool wrote:
> On most targets every function starts with moves from the parameter
> passing (hard) registers into pseudos. Similarly, after every call
> there is a move from the return register into a pseudo. These moves
> usually combine with later instructions
I plan to commit the attached patch this week if not told otherwise.
This is to generalize usage of C++11 direct initialization in unordered
containers.
It also avoids a number of safe iterator instantiations.
* include/debug/unordered_map
(unordered_map<>::begin()): Use C++11 direct
On most targets every function starts with moves from the parameter
passing (hard) registers into pseudos. Similarly, after every call
there is a move from the return register into a pseudo. These moves
usually combine with later instructions (leaving pretty much the same
instruction, just with a
Hi,
thanks for the comments.
>
> thanks for the proposal. The others have already expressed some of my
> worries and remarks, but I think it would be only right to write them
> again. Especially since I am part of the team responsible for
> implementation and maintenance of live patches here
On 10/20/18 9:47 AM, Giuliano Augusto Faulin Belinassi wrote:
> So I did some further investigation comparing the ULP error.
>
> With the formula that Wilco Dijkstra provided, there are cases where
> the substitution is super precise.
> With floats:
> with input : = 9.9940395355224609375
This test checks compile-time errors, so there's no point in trying to
actually run it.
Committed as obvious.
2018-10-22 Marek Polacek
PR testsuite/87694
* g++.dg/concepts/memfun-err.C: Make it a compile test.
--- gcc/testsuite/g++.dg/concepts/memfun-err.C
+++ gcc/testsuite/g
On 10/22/2018 09:08 AM, Bernd Edlinger wrote:
Hi!
This makes c_strlen avoid an unsafe strlen folding of const arguments
with non-const offset. Currently a negative out of bounds offset
makes the strlen function return an extremely large number, and
at the same time, prevents the VRP machinery,
Hi,
We should never use __vector long in the intrinsics compatibility headers,
since this has different meanings on 32- and 64-bit targets. This patch
corrects a number of places where this previously slipped through.
Bootstrapped and tested on powerpc64le-linux-gnu with no regressions.
Is this
Hi,
The vec_sel intrinsic is overloaded for multiple types. There are a
couple of cases in our intrinsic compatibility headers where the types
used don't match any allowable type signature. GCC is able to correctly
infer which matching built-in function is meant, but not all compilers
can. For
Target tests for the intrinsics defined in pmmintrin.h, copied from
gcc.target/i386.
Tested on POWER8 ppc64le and ppc64 (-m64 and -m32, the latter only reporting
16 new unsupported tests), and also by forcing -mcpu=power7 on ppc64.
[gcc/testsuite]
2018-10-22 Paul A. Clarke
* gcc.targ
This is a follow-on to earlier commits for adding compatibility
implementations of x86 intrinsics for PPC64LE. This patch adds
the 32 x86 intrinsics from ("SSSE3").
(Patch 2/2 adds tests for these intrinsics, and briefly describes
the tests performed.)
./gcc/ChangeLog:
2018-10-22 Paul A. Clar
On Mon, Oct 22, 2018 at 03:56:24PM +0100, Richard Earnshaw (lists) wrote:
> I think strongarm would be a better choice. I'm not aware of anyone
> running NetBSD on Arm8 cpus.
>
> Otherwise, this is fine with a suitable ChangeLog entry.
>
> R.
I hope this is OK. Thanks!
Maya Rashish
PR targe
Jason,
Do you have any suggestions for the C++ parts or are they good
enough to commit (with the expectation that I'll add template
handling later)?
The last patch is here:
https://gcc.gnu.org/ml/gcc-patches/2018-10/msg00811.html
Martin
On 10/16/2018 05:19 PM, Jeff Law wrote:
On 10/13/18 6:
Hi Rainer,
On 10/9/18 3:05 PM, Rainer Orth wrote:
> Hi Bernd,
>
>>> * The merge-all-constants-2.c test doesn't FAIL on Solaris/SPARC with
>>> /bin/as, although it lacks string merging support, too. The assembler
>>> output contains
>>>
>>> .section".rodata"
>>>
>>>
* Claudiu Zissulescu [2018-10-10 11:00:14 +0300]:
> Simple peephole rules which combines multiple ld/st instructions into
> 64-bit load/store instructions. It only works for architectures which
> are having double load/store option on.
>
> gcc/
> Claudiu Zissulescu
>
> * config/ar
* Claudiu Zissulescu [2018-10-10 11:00:15 +0300]:
> Reimplement how prologue and epilogue is emitted to accomodate
> enter/leave instructions, as well as improving the size of the
> existing techinques.
>
> The following modifications are added:
>
> - millicode thunk calls can be now selected r
Hi Thomas,
this patch is a collection of testcase patches we had, ready to be committed to
trunk.
I believe this only touches those parts where you can review, is this okay to
apply?
Thanks,
Chung-Lin
2018-10-22 Cesar Philippidis
gcc/testsuite/
* g++.dg/goacc/loop-1.c: New
On 22/10/2018 16:36, co...@sdf.org wrote:
> On Mon, Oct 22, 2018 at 03:56:24PM +0100, Richard Earnshaw (lists) wrote:
>> I think strongarm would be a better choice. I'm not aware of anyone
>> running NetBSD on Arm8 cpus.
>
> Clarifying: this is the global default for all GCC ARM targets,
> not ju
On Mon, Oct 22, 2018 at 03:56:24PM +0100, Richard Earnshaw (lists) wrote:
> I think strongarm would be a better choice. I'm not aware of anyone
> running NetBSD on Arm8 cpus.
Clarifying: this is the global default for all GCC ARM targets,
not just netbsd. Is strongarm still the preferred choice?
On Mon, Oct 22, 2018 at 5:00 AM, Martin Liška wrote:
> On 10/19/18 1:02 AM, Ian Lance Taylor wrote:
>> On Sat, Sep 22, 2018 at 12:08 PM, marxin wrote:
>>>
>>> gcc/go/ChangeLog:
>>>
>>> 2018-09-24 Martin Liska
>>>
>>> * gofrontend/escape.cc (Gogo::analyze_escape): Remove
>>> usa
Hi!
This makes c_strlen avoid an unsafe strlen folding of const arguments
with non-const offset. Currently a negative out of bounds offset
makes the strlen function return an extremely large number, and
at the same time, prevents the VRP machinery, to determine the correct
range if the strlen fun
Hi!
This fixes an ICE which was exposed by a previous patch of mine,
and a wrong transformation from strcat_chk => strcpy_chk,
which fails to adjust the object size, thus allowing too much
memory to be accessed.
Bootstrapped and reg-tested on x86_64-pc-linux-gnu.
Is it OK for trunk?
Thanks
Ber
On 21/10/2018 05:53, co...@sdf.org wrote:
> Regarding target/86383, it wasn't sufficient to not just pick arm6 for
> netbsd, as the default -mcpu is still arm6, which also fails to build.
>
> I assume the default is expected to be the oldest support, and I think
> now that's arm8, so maybe default
On Thu, 18 Oct 2018, Qing Zhao wrote:
> Hi,
>
> After more detailed study of GCC’s IPA optimizations, further study of the
> current available kernel live patching schemes and
> other live-patching user’s request, I came up with the following initial
> proposal in GCC to mainly support live-pa
On 04/10/2018 21:39, Richard Sandiford wrote:
OK with that change if it works, thanks.
Thanks, here's what I've committed.
Andrew
Don't double-count early-clobber matches.
Given a pattern with a number of operands:
(match_operand 0 "" "=&v")
(match_operand 1 "" " v0")
(match_operand 2 "" " v
On Mon, Oct 22, 2018 at 04:08:53PM +0200, Martin Liška wrote:
> Very valid question. I hope as long as I calculate the linear function
> values in wide_int (get via wi::to_wide (switch_element)), then it should
> overflow in the same way as original tree type arithmetic. I have a test-case
> with
On 10/22/18 4:17 PM, Alexander Monakov wrote:
> On Mon, 22 Oct 2018, Martin Liška wrote:
>
>> On 10/11/18 3:03 PM, Jakub Jelinek wrote:
>>> On Thu, Oct 11, 2018 at 02:56:14PM +0200, Martin Liška wrote:
As seen in the PR, switch conversion can do better when we return equal
numbers
On Mon, 22 Oct 2018, Martin Liška wrote:
> On 10/11/18 3:03 PM, Jakub Jelinek wrote:
> > On Thu, Oct 11, 2018 at 02:56:14PM +0200, Martin Liška wrote:
> >> As seen in the PR, switch conversion can do better when we return equal
> >> numbers
> >> based on index value. I implemented more than that,
On 10/17/18 12:39 AM, Jeff Law wrote:
> On 10/11/18 6:56 AM, Martin Liška wrote:
>> Hi.
>>
>> As seen in the PR, switch conversion can do better when we return equal
>> numbers
>> based on index value. I implemented more than that, more precisely I support
>> all linear
>> transformation based on
On 10/11/18 3:03 PM, Jakub Jelinek wrote:
> On Thu, Oct 11, 2018 at 02:56:14PM +0200, Martin Liška wrote:
>> As seen in the PR, switch conversion can do better when we return equal
>> numbers
>> based on index value. I implemented more than that, more precisely I support
>> all linear
>> transfor
On Mon, 22 Oct 2018, David Malcolm wrote:
> On Mon, 2018-10-22 at 15:56 +0200, Richard Biener wrote:
> [...snip...]
>
> > This is what I finally applied for the original patch after fixing
> > the above issue.
> >
> > Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
> >
> > Richard
On Mon, 2018-10-22 at 15:56 +0200, Richard Biener wrote:
[...snip...]
> This is what I finally applied for the original patch after fixing
> the above issue.
>
> Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
>
> Richard.
>
> 2018-10-22 Richard Biener
>
> * gimple-ssa-e
On Wed, 29 Aug 2018, Richard Biener wrote:
> On Wed, 29 Aug 2018, Jeff Law wrote:
>
> > On 08/29/2018 04:56 AM, Richard Biener wrote:
> > >
> > > In response to PR87105 I dusted off an old patch that adds an early
> > > phiopt pass. Recognizing we run phiopt twice with not many passes
> > > in
As the PR shows, the user can force this to be called on at least some
RTL that is not a valid address. Most targets treat this as if the
user knows best; let's do the same.
Committing to trunk.
Segher
2018-10-22 Segher Boessenkool
PR target/87598
* config/rs6000/rs6000.c
On Thu, 18 Oct 2018, Richard Biener wrote:
> On October 18, 2018 5:42:56 PM GMT+02:00, Aldy Hernandez
> wrote:
> >
> >
> >On 10/18/18 8:11 AM, Richard Biener wrote:
> >> On Thu, 18 Oct 2018, Richard Biener wrote:
> >>
> >>>
> >>> At some point we decided to not simply intersect all ranges we ge
On 8/28/18 12:10 PM, Richard Biener wrote:
> On Tue, Aug 28, 2018 at 9:11 AM Martin Liška wrote:
>>
>> On 08/27/2018 05:21 PM, Richard Biener wrote:
>>> On Mon, Aug 27, 2018 at 4:05 PM Martin Liška wrote:
Hi.
Now we should not meet a degenerated gswitch statements.
P
Just to follow up...
On 10/21/18 6:13 PM, Bill Schmidt wrote:
> On 10/20/18 10:53 AM, Segher Boessenkool wrote:
>> Hi!
>>
>> On Fri, Oct 19, 2018 at 04:27:27PM -0500, Bill Schmidt wrote:
>>> The x86 intrinsic compatibility headers contain a couple of instances of
>>> undefined behavior where a ca
On 10/16/18 6:57 PM, James Greenhalgh wrote:
> On Mon, Oct 08, 2018 at 05:34:52AM -0500, Martin Liška wrote:
>> Hi.
>>
>> I'm attaching updated version of the patch.
>
> Can't say I'm thrilled by the allocation/free (aarch64_parse_extension
> allocates, everyone else has to free) responsibilities
Ping 2.
On 10/11/18 6:33 PM, Richard Henderson wrote:
> Ping.
>
> On 10/2/18 9:19 AM, Richard Henderson wrote:
>> Changes since v1:
>> * Use config/t-slibgcc-libgcc instead of gcc.c changes.
>> * Some style fixes.
>> * Ifdefs to work with old glibc.
>>
>> * Force TImode registers into eve
On 10/22/18 6:21 AM, Richard Biener wrote:
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
2018-10-22 Richard Biener
PR tree-optimization/87640
* tree-vrp.c (set_value_range_with_overflow): Decompose
incomplete result.
(extract_rang
On 10/22/18 12:09 PM, Jakub Jelinek wrote:
> On Mon, Oct 22, 2018 at 12:04:23PM +0200, Martin Liška wrote:
>>> I noticed that before the tests were run with all of
>>> -std=(c|gnu)++(98|11|14), now with no explict -std option. I wonder if
>>> this is an issue.
>>>
>>> Rainer
>>>
>>
>> Hello.
>
On 10/19/18 1:02 AM, Ian Lance Taylor wrote:
> On Sat, Sep 22, 2018 at 12:08 PM, marxin wrote:
>>
>> gcc/go/ChangeLog:
>>
>> 2018-09-24 Martin Liska
>>
>> * gofrontend/escape.cc (Gogo::analyze_escape): Remove
>> usage of a parameter.
>> (Gogo::assign_connectivity): Likew
Committed.
2018-10-22 Richard Biener
* gcc.dg/graphite/scop-4.c: Avoid out-of-bound access.
Index: gcc/testsuite/gcc.dg/graphite/scop-4.c
===
--- gcc/testsuite/gcc.dg/graphite/scop-4.c (revision 265315)
+++ gcc/tes
This extends the treatment of Unchecked_Conversion between integral types and
aggregates types with reverse scalar storage order to floating-point types.
Tested on x86_64-suse-linux, applied on mainline, 8 and 7 branches.
2018-10-22 Eric Botcazou
* gcc-interface/utils.c (unchecked_c
This avoids spurious errors on x86 when the register pressure is too high, for
example on ACATS cxh3002:
cxh3002.adb: In function 'CXH3002':
cxh3002.adb:103:5: error: unsupported size for integer register
Tested on x86_64-suse-linux, applied on mainline, 8 and 7 branches.
2018-10-22 Eric Botca
On Sat, 20 Oct 2018, Richard Sandiford wrote:
> Richard Biener writes:
> > On Fri, 19 Oct 2018, Richard Sandiford wrote:
> >
> >> Richard Biener writes:
> >> > On October 18, 2018 11:05:32 PM GMT+02:00, Richard Sandiford
> >> > wrote:
> >> >>During recent stage3s I've tried to look at profiles
Bootstrapped on x86_64-unknown-linux-gnu, applied.
Richard.
2018-10-22 Richard Biener
PR middle-end/87682
* mem-stats.h (mem_usage::operator==): Fix pasto.
Index: gcc/mem-stats.h
===
--- gcc/mem-stats.h (re
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
2018-10-22 Richard Biener
PR tree-optimization/87640
* tree-vrp.c (set_value_range_with_overflow): Decompose
incomplete result.
(extract_range_from_binary_expr_1): Adjust.
* gcc.d
On Sun, Oct 21, 2018 at 10:52 AM Yuri Gribov wrote:
>
> Hi all,
>
> My recent patch which replaced
> (float_type)int_var1 CMP (float_type)int_var2
> with
> int_var1 CMP int_var2
> may generate unordered comparisons of integer values which are both
> unnecessary and may also upset later passes.
@honza: PING
On 10/3/18 12:53 PM, Martin Liška wrote:
> On 10/3/18 11:04 AM, Jan Hubicka wrote:
>>>
>>> That was promised to be done by Honza Hubička. He's very skilled in IPA
>>> optimizations and he's aware
>>> of optimizations that cause troubles for live-patching.
>>
>> :) I am not sure how s
On Mon, Oct 22, 2018 at 12:04:23PM +0200, Martin Liška wrote:
> > I noticed that before the tests were run with all of
> > -std=(c|gnu)++(98|11|14), now with no explict -std option. I wonder if
> > this is an issue.
> >
> > Rainer
> >
>
> Hello.
>
> I guess that should not be a problem.
I
On 10/12/18 10:20 AM, Rainer Orth wrote:
> Hi Martin,
>
>> On 10/9/18 11:03 AM, Rainer Orth wrote:
>>> Hi Martin,
>>>
rename from gcc/testsuite/g++.dg/ext/pr82625.C
rename to gcc/testsuite/g++.target/i386/pr82625.C
index 59b174f8c51..0eb70baed5e 100644
--- a/gcc/testsuite/g++.d
Hi all,
This patch replaces the umov instruction in the aarch64 popcount expansion with
the less expensive fmov instruction.
Example:
int foo (int a) {
return __builtin_popcount (a);
}
would generate:
foo:
uxtw x0, w0
fmov d0, x0
cnt v0.8b, v0.8b
addv b0, v0.8b
umov w0, v0.b
Hi Gerald,
> On Tue, 16 Oct 2018, Rainer Orth wrote:
>> The following patch documents the Solaris 10 obsoletion in the GCC 9
>> changes.html. I've based this on the GCC 4.9 text which allowed for
>> obsoletion of several targets. Tested by inspection in Firefox.
>>
>> Ok to install?
>
> Yes. A
On 19.10.18 10:39, Ilya Leoshkevich wrote:
> gcc/ChangeLog:
>
> 2018-10-18 Ilya Leoshkevich
>
> * config/s390/s390.c (s390_loadrelative_operand_p): Accept
> literal pool references.
> (s390_check_qrst_address): Adapt to the new behavior of
> s390_loadrelative_operand_p
On Sat, 20 Oct 2018, Martin Jambor wrote:
> Hi,
>
> This long patch only does one simple thing, adds an explicit function
> parameter to predicates stmt_could_throw_p, stmt_can_throw_external
> and stmt_can_throw_internal.
>
> My motivation was ability to use stmt_can_throw_external in IPA
> ana
80 matches
Mail list logo
