On Mon, Nov 14, 2016 at 11:56 PM, kugan
wrote:
> Hi Richard,
>
> On 08/11/16 23:45, Richard Biener wrote:
>>
>> On Tue, Nov 8, 2016 at 3:32 AM, kugan
>> wrote:
>>>
>>> Hi,
>>>
>>> In tree-ssa-coalesce, register_ssa_partition ) and
>>> register_ssa_partition_check have lost their meaning over vari
On Mon, Nov 14, 2016 at 11:13 PM, Jerry DeLisle wrote:
> On 11/13/2016 11:03 PM, Thomas Koenig wrote:
>>
>> Hi Jerry,
>>
>> I think this
>>
>> + /* Parameter adjustments */
>> + c_dim1 = m;
>> + c_offset = 1 + c_dim1;
>>
>> should be
>>
>> + /* Parameter adjustments */
>> +
On 14 November 2016 at 21:31, Ramana Radhakrishnan
wrote:
>
> On Mon, 14 Nov 2016 at 19:59, Christophe Lyon
> wrote:
>>
>> On 14 November 2016 at 18:54, Mike Stump wrote:
>> > On Oct 21, 2016, at 1:00 AM, Christophe Lyon
>> > wrote:
>> >>
>> >> So if we say that the current behaviour has to kee
> Thanks for the patch. I'm a bit concerned about the interaction this
> will have with microMIPS which can (albeit not implemented today) use
> 2-byte alignment on function entry points.
>
> Is the solution for other targets to mandate 4-byte alignment when
> using function descriptors?
Yes, the
On 14 November 2016 at 22:51, Ville Voutilainen
wrote:
> On 14 November 2016 at 22:49, Ville Voutilainen
> wrote:
>> I needed to do some minor tweaks in
>> testsuite/20_util/in_place/requirements.cc. I committed the attached
>> after testing the full suite on Linux-PPC64.
>
>
> P.S. make_unsigned
On Mon, Nov 14, 2016 at 11:53:55PM -0500, Jason Merrill wrote:
> The standard says that references that refer to a constant address can
> be used in a constant-expression, but we haven't allowed that. This
> patch implements it, but without the parser.c hunk it broke
> libgomp.c++/target-14.C.
Th
Please find attached the revised patch as requested.
Ok to apply?
Claudiu
gcc/
2016-05-09 Claudiu Zissulescu
* config/arc/arc-arch.h: New file.
* config/arc/arc-arches.def: Likewise.
* config/arc/arc-cpus.def: Likewise.
* config/arc/arc-options.def: Likewise.
On Fri, Nov 11, 2016 at 02:17:58PM -0600, Segher Boessenkool wrote:
> On Fri, Nov 11, 2016 at 09:58:21AM +0100, Dominik Vogt wrote:
> > > You say it needs more testing -- what testing?
> >
> > Regression testing on AIX (David has done this in reply to the
> > original message), possibly also on 32
> Can you verify that a TU compiled with -fstrict-aliasing will link as
> if -fno-strict-aliasing if -fno-strict-aliasing is specified at link time?
Yes, it does:
eric@polaris:~/build/gcc/native> ~/install/gcc/bin/gcc -c t.c -O2 -flto
eric@polaris:~/build/gcc/native> ~/install/gcc/bin/gcc -o t t.
On Mon, Nov 14, 2016 at 7:28 PM, Andrew Senkevich
wrote:
> 2016-11-11 14:16 GMT+03:00 Uros Bizjak :
>> The x86 part of the patch is OK with the above changes and additional
>> target attribute test for flags2 ISA features..
>
> Fixed according your comments, I will followup with additional tests s
[ This patch is part of the SVE series posted here:
https://gcc.gnu.org/ml/gcc/2016-11/msg00030.html ]
The old assignment to bitwidth was before we handled VOIDmode with:
if (mode == VOIDmode)
mode = GET_MODE (x);
so when VOIDmode was specified we would always use:
if (bitwidth < GET_
> 2016-11-15 Richard Sandiford
> Alan Hayward
> David Sherwood
>
> * rtlanal.c (num_sign_bit_copies1): Calculate bitwidth after
> handling VOIDmode.
OK, thanks, but please change the comment too, I think "For a smaller mode"
would be less confusing.
--
So far all target implementations of the separate shrink-wrapping hooks
use the DF LIVE info to figure out around which basic blocks the non-
volatile registers need to be saved. This is done by looking at the
IN+GEN+KILL sets of the basic blocks. However, that doesn't work for
registers that DF
[ This patch is part of the SVE series posted here:
https://gcc.gnu.org/ml/gcc/2016-11/msg00030.html ]
simplify_shift_const_1 handles both shifts of scalars by scalars
and shifts of vectors by scalars. For vectors this means that
each element is shifted by the same amount.
However:
(a) the tw
This patch removes some references to gcj in the top level and config
directories and in the gcc documentation. The change to the config directory
requires regenerating aclocal.m4 and configure in each sub directory.
Ok for the trunk?
Matthias
2016-11-14 Matthias Klose
* config-ml
...it should have been checking the size instead.
Tested on aarch64-linux-gnu and x86_64-linux-gnu. Committed as obvious.
Thanks,
Richard
[ This patch is part of the SVE series posted here:
https://gcc.gnu.org/ml/gcc/2016-11/msg00030.html ]
gcc/
2016-11-15 Richard Sandiford
A
Hi!
The genattrtab build-tool uses way too much memory in general.
I think there is no other build step that uses more memory.
On the currently trunk it takes around 700MB to build the
ARM latency tab files. I debugged that yesterday
and found that this can be reduced to 8MB (!). Yes, really.
Seen while cleaning up the GCJ references. The last section of the gcj install
docs doesn't belong there, but into the cross install section. The change is
not necessary on the trunk once the gcj docs are removed. Fixed this on the 5
and 6 branches by moving the section.
Committed as obvious.
Hi!
On Mon, Nov 14, 2016 at 04:43:35PM -0700, Kelvin Nilsen wrote:
> * config/rs6000/altivec.md (UNSPEC_CMPRB): New unspec value.
> (UNSPEC_CMPRB2): New unspec value.
I wonder if you really need both? The number of arguments will tell
which is which, anyway?
> (cmprb_p): New e
If we use ABI_V4 and we have a big stack frame, we end the epilogue
with a "mr 1,11" (or similar) instruction. This instruction however
has no dependencies on the earlier restores from stack (done via r11),
so sched2 can end up reordering the insns, which is bad because we
have no red zone so that
On 14/11/16 14:32 +0100, Christophe Lyon wrote:
On 20 October 2016 at 19:40, Jonathan Wakely wrote:
On 20/10/16 10:33 -0700, Mike Stump wrote:
On Oct 20, 2016, at 9:34 AM, Jonathan Wakely wrote:
On 20/10/16 09:26 -0700, Mike Stump wrote:
On Oct 20, 2016, at 5:20 AM, Jonathan Wakely wro
On Tue, Nov 15, 2016 at 10:47 AM, Eric Botcazou wrote:
>> Can you verify that a TU compiled with -fstrict-aliasing will link as
>> if -fno-strict-aliasing if -fno-strict-aliasing is specified at link time?
>
> Yes, it does:
>
> eric@polaris:~/build/gcc/native> ~/install/gcc/bin/gcc -c t.c -O2 -flt
Hi Richard,
On Tue, Nov 15, 2016 at 10:49:26AM +, Richard Sandiford wrote:
> simplify_shift_const_1 handles both shifts of scalars by scalars
> and shifts of vectors by scalars. For vectors this means that
> each element is shifted by the same amount.
>
> However:
>
> (a) the two cases were
On 12/11/16 12:11 -0800, Tim Shen wrote:
At Issaquah we decided to remove the supports above.
OK with a suitable ChangeLog, thanks.
> Yes, I know -fno-strict-aliasing is globally set, but will all
> -fstrict-aliasing optimization attributes on functions be "overwritten"?
> That is, are you sure that when optimizing a function originally compiled
> with -fstrict-aliasing that -fno-strict-aliasing is in effect?
Do you mean with
Bernd Edlinger writes:
> Hi!
>
> The genattrtab build-tool uses way too much memory in general.
> I think there is no other build step that uses more memory.
>
> On the currently trunk it takes around 700MB to build the
> ARM latency tab files. I debugged that yesterday
> and found that this can
Hi Andrew,
Thanks for the patch and looking into this.
On Mon, Nov 14, 2016 at 04:57:58PM +, Andrew Stubbs wrote:
> The testcase powerpc/fusion3.c causes an ICE when compiled with
> -msoft-float.
> Basically, the problem is that the peephole optimization tries to create
> a Power9 Fusion i
The transformations made by make_compound_operation apply
only to scalar integer modes. The fix for PR70944 had enforced
that by returning early for vector modes at the top of the
function. However, the function is supposed to be recursive,
so we should continue to look at integer suboperands eve
LOAD_EXTEND_OP only applies to scalar integer modes that are narrower
than a word. However, callers weren't consistent about which of these
checks they made beforehand, and also weren't consistent about whether
"smaller" was based on (bit)size or precision (IMO it's the latter).
This patch adds a
We previously stored the number of loop iterations rather
than the number of latch iterations.
Tested on aarch64-linux-gnu and x86_64-linux-gnu. OK to install?
Thanks,
Richard
[ This patch is part of the SVE series posted here:
https://gcc.gnu.org/ml/gcc/2016-11/msg00030.html ]
gcc/
2016-11
2016-11-11 14:16 GMT+03:00 Uros Bizjak :
> --- a/gcc/genmodes.c
> +++ b/gcc/genmodes.c
> --- a/gcc/init-regs.c
> +++ b/gcc/init-regs.c
> --- a/gcc/machmode.h
> +++ b/gcc/machmode.h
>
> These are middle-end changes, you will need a separate review for these.
Who could review these changes?
--
WBR
vect_transform_loop has to reduce three iteration counts by
the vectorisation factor: nb_iterations_upper_bound,
nb_iterations_likely_upper_bound and nb_iterations_estimate.
All three are latch execution counts rather than loop body
execution counts. The calculations were taking that into
account
On Tue, Nov 15, 2016 at 12:33:06PM +, Richard Sandiford wrote:
> The transformations made by make_compound_operation apply
> only to scalar integer modes. The fix for PR70944 had enforced
> that by returning early for vector modes at the top of the
> function. However, the function is suppose
Hi!
This test fails on i686-linux (and perhaps on powerpc* too) due to -Wpsabi
warnings. Fixed thusly, committed as obvious to trunk.
2016-11-15 Jakub Jelinek
PR middle-end/78295
* gcc.dg/uninit-pr78295.c: Add -Wno-psabi to dg-options.
--- gcc/testsuite/gcc.dg/uninit-pr78295
Hi,
The branch-cost-1.c test uses the isa>=4 option to ensure the existence of the
MOVN/MOVZ instructions. This, however, does not take into account R6 targets,
which are accepted by the isa>=4 option but do not support MOVN/MOVZ.
This particular test does not fail on R6, because it is checking f
Hi!
On Mon, Nov 14, 2016 at 10:58:51AM +0100, Jakub Jelinek wrote:
> Working virtually out of Samoa.
>
> The following patch is an attempt to handle -fsanitize=undefined
> for vectors. We already diagnose out of bounds accesses for vector
> subscripts, this patch adds expansion for vector UBSAN_
On Tue, Nov 15, 2016 at 6:48 AM, Segher Boessenkool
wrote:
> If we use ABI_V4 and we have a big stack frame, we end the epilogue
> with a "mr 1,11" (or similar) instruction. This instruction however
> has no dependencies on the earlier restores from stack (done via r11),
> so sched2 can end up re
Hi!
On the following testcase we ICE, because the underlying artificial decls
have NULL DECL_NAME (intentional), thus mangling is not able to figure out
what to do. This patch attempts to follow the
http://sourcerytools.com/pipermail/cxx-abi-dev/2016-August/002951.html
proposal (and for error rec
Hi!
This patch adds 3 new tests. Tested on x86_64-linux, ok for trunk?
2016-11-15 Jakub Jelinek
* g++.dg/cpp1z/decomp13.C: New test.
* g++.dg/cpp1z/decomp14.C: New test.
* g++.dg/cpp1z/decomp15.C: New test.
--- gcc/testsuite/g++.dg/cpp1z/decomp13.C.jj2016-11-15 1
This implements the resolution to LWG 2748 which was approved the
other day at the WG21 meeting. I think the resolution is wrong,
because as the test shows it means that optional is
swappable in some cases. I've raised that with the LWG and will
probably create a new issue for it, but in the meant
This is another issue resolution for C++17 features that was approved
at the recent meeting. I think this resolution is wrong too, but in
this case the fix is obvious so I've gone ahead and done it.
* doc/xml/manual/intro.xml: Document LWG 2742 status.
* doc/html/*: Regenerate.
There are 138 test files that says "a moved_to of the GNU General
Public License", presumably from a find& replace that then got copied
to new tests.
Fixed as obvious, as shown by this patch (the full patch is too big
for the mailing list).
commit 4ae2edc3c515f76e02712f744a0e3081de94be18
Author:
On Thu, Nov 10, 2016 at 10:50:27PM +0100, Jakub Jelinek wrote:
> > + self(); // error: use of 'decltype(auto)
> > fix_type::operator()() [with Functor = main()::]'
> > before deduction of 'auto'
>
> Wouldn't it be clearer to turn that // error: line into
> // { dg-bogus "use of \[^\n\r]* b
Hi All,
Here is patch for non-masked epilogue vectoriziation.
Bootstrap and regression testing did not show any new failures.
Is it OK for trunk?
Thanks.
Changelog:
2016-11-15 Yuri Rumyantsev
* params.def (PARAM_VECT_EPILOGUES_NOMASK): New.
* tree-if-conv.c (tree_if_conversion): Make publi
On 15/11/16 14:36 +, Jonathan Wakely wrote:
There are 138 test files that says "a moved_to of the GNU General
Public License", presumably from a find& replace that then got copied
to new tests.
Fixed as obvious, as shown by this patch (the full patch is too big
for the mailing list).
Fixed
On Tue, Nov 15, 2016 at 4:32 AM, Jakub Jelinek wrote:
> So, is there a way to treat references the similarly? I.e. only "fold"
> reference vars to what they refer (DECL_INITIAL) in constexpr.c evaluation,
> or gimplification where a langhook or omp_notice_variable etc. has the
> last say on when
On 11/15/2016 05:55 AM, Andrew Senkevich wrote:
2016-11-11 14:16 GMT+03:00 Uros Bizjak :
--- a/gcc/genmodes.c
+++ b/gcc/genmodes.c
--- a/gcc/init-regs.c
+++ b/gcc/init-regs.c
--- a/gcc/machmode.h
+++ b/gcc/machmode.h
These are middle-end changes, you will need a separate review for these.
Who
Appearantly for some unknown reason we refuse to inline anything into
functions calling cilk_spawn. That breaks fortified headers and
all other always-inline function calls (intrinsics come to my mind as
well).
Bootstrapped and tested on x86_64-unknown-linux-gnu, ok for trunk?
Thanks,
Richard.
> From: gcc-patches-ow...@gcc.gnu.org [mailto:gcc-patches-
> ow...@gcc.gnu.org] On Behalf Of Toma Tabacu
> Sent: 15 November 2016 14:00
> To: gcc-patches@gcc.gnu.org
> Cc: Matthew Fortune; catherine_mo...@mentor.com
> Subject: [PATCH,testsuite] MIPS: Downgrade from R6 to R5 to prevent
> redundant
> This looks fine. Thanks for all your effort revising this patch.
>
> Andrew
>
Committed r242425.
Thank you for your review,
Claudiu
On Tue, Nov 15, 2016 at 1:44 PM, Richard Sandiford
wrote:
> We previously stored the number of loop iterations rather
> than the number of latch iterations.
So ->nb_iterations was unused without SVE? Otherwise can you please
add a testcase?
Thanks,
Richard.
> Tested on aarch64-linux-gnu and x8
Hi!
I've fixed this PR already in r240198 as part of the PR77482
fix, thus I've just added the testcase for it. Tested on x86_64-linux,
committed to trunk as obvious.
2016-11-15 Jakub Jelinek
PR c++/71988
* g++.dg/cpp0x/constexpr-71988.C: New test.
--- gcc/testsuite/g++.dg/c
On Tue, Nov 15, 2016 at 1:19 PM, Eric Botcazou wrote:
>> Yes, I know -fno-strict-aliasing is globally set, but will all
>> -fstrict-aliasing optimization attributes on functions be "overwritten"?
>> That is, are you sure that when optimizing a function originally compiled
>> with -fstrict-aliasing
On Tue, Nov 15, 2016 at 1:57 PM, Richard Sandiford
wrote:
> vect_transform_loop has to reduce three iteration counts by
> the vectorisation factor: nb_iterations_upper_bound,
> nb_iterations_likely_upper_bound and nb_iterations_estimate.
> All three are latch execution counts rather than loop body
On Mon, Nov 14, 2016 at 3:39 PM, Mark Wielaard wrote:
> When construction a :? or fold expression that requires a third
> expression only the first and second were explicitly checked to
> not be NULL. Since the third expression is also required in these
> constructs it needs to be explicitly check
PING! Once the new options are in, we need also to update the tests.
Andrew, please can you check it,
Claudiu
> -Original Message-
> From: Claudiu Zissulescu
> Sent: Monday, May 30, 2016 2:33 PM
> To: gcc-patches@gcc.gnu.org
> Cc: Claudiu Zissulescu ; g...@amylaar.uk;
> francois.bed...@s
On 11/15/2016 07:03 AM, Jakub Jelinek wrote:
Hi!
On Mon, Nov 14, 2016 at 10:58:51AM +0100, Jakub Jelinek wrote:
Working virtually out of Samoa.
The following patch is an attempt to handle -fsanitize=undefined
for vectors. We already diagnose out of bounds accesses for vector
subscripts, this
> Is there a reason that instruction should be uppercase?
>
> This otherwise looks fine to me.
>
Committed r242428.
Thank you for your review,
Claudiu
On 11/15/2016 03:55 AM, Matthias Klose wrote:
This patch removes some references to gcj in the top level and config
directories and in the gcc documentation. The change to the config directory
requires regenerating aclocal.m4 and configure in each sub directory.
Ok for the trunk?
Matthias
2
OK.
On Tue, Nov 15, 2016 at 9:39 AM, Jakub Jelinek wrote:
> On Thu, Nov 10, 2016 at 10:50:27PM +0100, Jakub Jelinek wrote:
>> > + self(); // error: use of 'decltype(auto)
>> > fix_type::operator()() [with Functor =
>> > main()::]' before deduction of 'auto'
>>
>> Wouldn't it be clearer to
Richard Biener writes:
> On Tue, Nov 15, 2016 at 1:44 PM, Richard Sandiford
> wrote:
>> We previously stored the number of loop iterations rather
>> than the number of latch iterations.
>
> So ->nb_iterations was unused without SVE? Otherwise can you please
> add a testcase?
TBH I can't remembe
On 11/14/2016 11:22 PM, Thomas Koenig wrote:
Hi Jerry,
With these changes, OK for trunk?
Just going over this with a fine comb...
One thing just struck me: The loop variables should be index_type, so
const index_type m = xcount, n = ycount, k = count;
[...]
index_type a_dim1, a
On 11/11/16 19:38, Jakub Jelinek wrote:
On Fri, Nov 11, 2016 at 06:21:48PM +, Jiong Wang wrote:
This patch introduces three AARCH64 private DWARF operations in vendor extension
space.
DW_OP_AARCH64_pauth 0xea
===
Takes one unsigned LEB 128 Pointer Authentication Description. Bits [3:0]
On 11/15/2016 05:42 AM, Richard Sandiford wrote:
LOAD_EXTEND_OP only applies to scalar integer modes that are narrower
than a word. However, callers weren't consistent about which of these
checks they made beforehand, and also weren't consistent about whether
"smaller" was based on (bit)size or
alias.c encodes memory sizes as follows:
size > 0: the exact size is known
size == 0: the size isn't known
size < 0: the exact size of the reference itself is known,
but the address has been aligned via AND. In this case
"-size" includes the size of the reference and the worst-case
number o
After simplifying the operands of a PLUS, canon_rtx checked only
for cases in which one of the simplified operands was a constant,
falling back to gen_rtx_PLUS otherwise. This left the PLUS in a
non-canonical order if one of the simplified operands was
(plus (reg R1) (const_int X)); we'd end up wi
When fpu trapping is enabled in libgfortran, the return value of
feenableexcept is not checked. Glibc reports there if the operation
was unsuccessful which happens if the target has no trapping support.
There seems to be a separate api for checking trapping support:
ieee_support_halting, but it o
On 11/15/2016 09:07 AM, Richard Sandiford wrote:
After simplifying the operands of a PLUS, canon_rtx checked only
for cases in which one of the simplified operands was a constant,
falling back to gen_rtx_PLUS otherwise. This left the PLUS in a
non-canonical order if one of the simplified operand
The previous code processed the users of a stack slot in order of
decreasing size and allocated the slot based on the first user.
This seems a bit dangerous, since the ordering is based on the
mode of the biggest reference while the allocation is based also
on the size of the register itself (which
Using MEM_SIZE is more general, since it copes with cases where
targets are forced to use BLKmode references for whatever reason.
Thanks,
Richard
[ This patch is part of the SVE series posted here:
https://gcc.gnu.org/ml/gcc/2016-11/msg00030.html ]
gcc/
2016-11-15 Richard Sandiford
On Tue, Nov 15, 2016 at 04:00:40PM +, Jiong Wang wrote:
> >> Takes one signed LEB128 offset and retrieves 8-byte contents from the
> >> address
> >> calculated by CFA plus this offset, the contents then authenticated as
> >> per A
> >> key for instruction pointer using current CFA as sa
On 11/14/2016 02:39 AM, Jeff Law wrote:
I was looking at the possibility of dropping threading from VRP1/VRP2 or
DOM1/DOM2 in favor of the backwards threader -- the obvious idea being
to recover some compile-time for gcc-7.
Of the old-style threader passes (VRP1, VRP2, DOM1, DOM2), VRP2 is by
If the size passed in to rtx_addr_can_trap_p was zero, the frame
handling would get the size from the mode instead. However, this
too can be zero if the mode is BLKmode, i.e. if we have a BLKmode
memory reference with no MEM_SIZE (which should be rare these days).
This meant that the conditions fo
On 11/15/2016 09:17 AM, Richard Sandiford wrote:
Using MEM_SIZE is more general, since it copes with cases where
targets are forced to use BLKmode references for whatever reason.
Thanks,
Richard
[ This patch is part of the SVE series posted here:
https://gcc.gnu.org/ml/gcc/2016-11/msg00030.h
Hi,
> There seems to be a separate api for checking trapping support:
> ieee_support_halting, but it only checked if the exception status
> flags are available, so check trapping support too by enabling
> and disabling traps.
Thanks for the patch.
I am worried about the unnecessary operations th
Maciej Rozycki writes:
> gcc/
> * config/mips/mips-protos.h (mips_set_text_contents_type): New
> prototype.
> * config/mips/mips.h (ASM_OUTPUT_BEFORE_CASE_LABEL): New macro.
> (ASM_OUTPUT_CASE_END): Likewise.
> * config/mips/mips.c (mips_set_text_contents_type):
The CONCAT handling in emit_group_load chooses between doing
an extraction from a single component or forcing the whole
thing to memory and extracting from there. The condition for
the former (more efficient) option was:
if ((bytepos == 0 && bytelen == slen0)
|| (bytepos !
Hi all,
attached patch fixes the issue raised. The issue here was, that a copy of the
base class was generated and its address passed to the _vptr->copy()-method,
which then accessed memory, that was not present in the copy being an object of
the base class. The patch fixes this by making sure the
2016-11-15 17:56 GMT+03:00 Jeff Law :
> On 11/15/2016 05:55 AM, Andrew Senkevich wrote:
>>
>> 2016-11-11 14:16 GMT+03:00 Uros Bizjak :
>>>
>>> --- a/gcc/genmodes.c
>>> +++ b/gcc/genmodes.c
>>> --- a/gcc/init-regs.c
>>> +++ b/gcc/init-regs.c
>>> --- a/gcc/machmode.h
>>> +++ b/gcc/machmode.h
>>>
>>>
OK, (hopefully) one more patch for decltype and C++17 decomposition
declarations. I hadn't been thinking that "referenced type" meant to
look through references in the tuple case, since other parts of
[dcl.decomp] define "the referenced type" directly, but that does seem
to be how it's used elsewh
Provide versions of subreg_lowpart_offset and subreg_highpart_offset
that work on mode sizes rather than modes. Also provide a routine
that converts an lsb position to a subreg offset.
The intent (in combination with later patches) is to move the
handling of the BYTES_BIG_ENDIAN != WORDS_BIG_ENDI
local_cprop_find_used_regs punted on all multiword registers,
with the comment:
/* Setting a subreg of a register larger than word_mode leaves
the non-written words unchanged. */
But this only applies if the outer mode is smaller than the
inner mode. If they're the same size then
On 11/01/2016 03:39 PM, Wilco Dijkstra wrote:
Jeff Law wrote:
I think you'll need to look at bz61320 before this could go in.
I had a look, but there is nothing there that is related - eventually
a latent alignment bug was fixed in IVOpt.
Excellent. Thanks for digging into what really hap
On 11/15/2016 07:59 AM, Jerry DeLisle wrote:
On 11/14/2016 11:22 PM, Thomas Koenig wrote:
Hi Jerry,
With these changes, OK for trunk?
Just going over this with a fine comb...
One thing just struck me: The loop variables should be index_type, so
const index_type m = xcount, n = ycou
On 15/11/16 16:22, FX wrote:
>> There seems to be a separate api for checking trapping support:
>> ieee_support_halting, but it only checked if the exception status
>> flags are available, so check trapping support too by enabling
>> and disabling traps.
>
> Thanks for the patch.
>
> I am worried
This isn't intended to change the behaviour, just rewrite the
existing logic in a different (and hopefully clearer) way.
The new form -- particularly the part based on the "block"
concept -- is easier to convert to polynomial sizes.
Tested on aarch64-linux-gnu and x86_64-linux-gnu. OK to install?
On 11/15/2016 09:21 AM, Richard Sandiford wrote:
If the size passed in to rtx_addr_can_trap_p was zero, the frame
handling would get the size from the mode instead. However, this
too can be zero if the mode is BLKmode, i.e. if we have a BLKmode
memory reference with no MEM_SIZE (which should be
Hi.
As seen on ppc64le during compilation of Firefox with LTO, combining inchash
value
with a pointer, enum value and an integer, one can eventually get zero value.
Thus I decided to introduce a new flag that would distinguish between not set
hash value
and a valid and (possibly) zero value.
I'
On 11/15/2016 09:43 AM, Martin Liška wrote:
Hi.
As seen on ppc64le during compilation of Firefox with LTO, combining inchash
value
with a pointer, enum value and an integer, one can eventually get zero value.
Thus I decided to introduce a new flag that would distinguish between not set
hash va
> Hi.
>
> As seen on ppc64le during compilation of Firefox with LTO, combining inchash
> value
> with a pointer, enum value and an integer, one can eventually get zero value.
> Thus I decided to introduce a new flag that would distinguish between not set
> hash value
> and a valid and (possibly)
Richard Sandiford writes:
> This isn't intended to change the behaviour, just rewrite the
> existing logic in a different (and hopefully clearer) way.
> The new form -- particularly the part based on the "block"
> concept -- is easier to convert to polynomial sizes.
>
> Tested on aarch64-linux-gnu
On Fri, Oct 7, 2016 at 1:01 AM, Kyrill Tkachov
wrote:
> Hi Andrew,
>
>
> On 24/09/16 06:46, Andrew Pinski wrote:
>>
>> Hi,
>>As reported in PR 61367, the aarch64 back-end is too verbose when it
>> is dealing with the cost model. I tend to agree, no other back-end is
>> this verbose. So I dec
On 15/11/16 16:18, Jakub Jelinek wrote:
On Tue, Nov 15, 2016 at 04:00:40PM +, Jiong Wang wrote:
Takes one signed LEB128 offset and retrieves 8-byte contents from the address
calculated by CFA plus this offset, the contents then authenticated as per A
key for instruction pointer us
vec_cmps assign the result of a vector comparison to a mask.
The optab was called with the destination having mode mask_mode
but with the source (the comparison) having mode VOIDmode,
which led to invalid rtl if the source operand was used directly.
Tested on aarch64-linux-gnu and x86_64-linux-gnu
On 15/11/16 16:18, Jakub Jelinek wrote:
On Tue, Nov 15, 2016 at 04:00:40PM +, Jiong Wang wrote:
Takes one signed LEB128 offset and retrieves 8-byte contents from the address
calculated by CFA plus this offset, the contents then authenticated as per A
key for instruction pointer usin
On 15/11/16 12:29, Segher Boessenkool wrote:
The peepholes do not support it, or maybe the define_insns do not either.
The machine of course will not care.
Oh, OK, so probably the bug is not in the peephole at all, but in the
define_insn, or lack thereof.
More investigation required.
Thanks
On Mon, 14 Nov 2016, Alexander Monakov wrote:
> On Mon, 14 Nov 2016, Martin Jambor wrote:
>
> > Hi,
> >
> > yesterday I forgot to send out the following patch. The test
> > libgomp/testsuite/libgomp.fortran/examples-4/device-3.f90 was failing
> > for me when I was testing the HSA branch merge bu
Several definitions of INCOMING_RETURN_ADDR_RTX used
gen_rtx_REG (VOIDmode, ...), which with later patches
would trip an assert. This patch converts them to use
Pmode instead.
Tested on aarch64-linux-gnu and x86_64-linux-gnu. OK to install?
Thanks,
Richard
[ This patch is part of the SVE seri
> disabling/enabling makes this api a lot heavier
> than before, but trapping cannot be decided at
> compile-time, although the result may be cached,
> i think this should not be a frequent operation.
>
> otoh rereading my patch i think i fail to restore
> the original exception state correctly.
On Mon, Nov 14, 2016 at 1:19 AM, Mark Wielaard wrote:
> In various situations the cplus_demangle () function could read past the
> end of input causing crashes. Add checks in various places to not advance
> the demangle string location and fail early when end of string is reached.
> Add various ex
1 - 100 of 164 matches
Mail list logo