On 05/14/2014 08:51 AM, Konstantin Serebryany wrote:
One theme I have been noticing in the libsanitizer code is that it has
all of the knowledge of glibc when it comes to syscalls but makes some
bad assumptions dealing with some structures. For an example on MIPS
n64: stat and stat64 are differe
2014-05-15 0:22 GMT+02:00 Jonathan Wakely :
> I found a bug in the new std::get(tuple&&) function
> where it didn't compile when trying to access reference member.
>
> The rest of this patch simplifies the code in by:
>
> - removing the redundant __add_ref etc. helpers.
> - defining a __tuple_elem
Hi All,
In AArch64 back-end, BASE_REG_CLASS is defined to be POINTER_REGS.
Shouldn’t this be GENERAL_REGS?
Attached RFC patch makes it GENERAL_REGS. Regression tested for
aarch64-none-linux-gnu on qemu-aarch64 with now new regression. Is this OK ?
Thanks,
Kugan
gcc/
2014-05-15 Kugan Vivekanand
On Wed, May 14, 2014 at 12:47:11PM -0400, Jason Merrill wrote:
> commit f770db5dce4328b831d3c3e50322366f3e7b927a
> Author: jason
> Date: Tue May 13 21:10:03 2014 +
>
> * call.c (print_error_for_call_failure): Say "no match" rather
> than "ambiguous" if there were no strict match
On 15 May 2014 02:03, Jeff Law wrote:
> On 05/13/14 03:49, Zhenqiang Chen wrote:
>>
>> On 9 May 2014 14:08, Jeff Law wrote:
>>>
>>> On 05/08/14 02:07, Zhenqiang Chen wrote:
Hi,
The patch splits the live_edge for move_insn_for_shrink_wrap to sink
the copy out of the e
David Edelsohn writes:
> Richard,
>
> Your SYMBOL_REF_FLAGS RTX patches broke bootstrap on AIX.
>
> - David
>
> /nasfarm/edelsohn/src/src/libgcc/libgcc2.c: In function '__eprintf':
> /nasfarm/edelsohn/src/src/libgcc/libgcc2.c:2126:1: internal compiler error:
> RTL
> flag check: SYMBOL_REF_FLAGS u
Hi!
fold_binary_loc for (X >> C1) & C2, if X is zero extended narrower
value, decreases prec, but if the shift count is bigger
than the narrower prec, we then attempt to zerobits <<= negative_value.
In that case the result is necessarily zero though, all possibly non-zero
bits are shifted away, s
On 05/14/14 14:34, Alan Lawrence wrote:
In final testing I noticed that vtrnf32_1.c, vtrns32_1.c and vtrnu32_1.c were
failing the scan-assembler-times test: in such two-element cases, TRN, UZP and
ZIP are all equivalent and equally valid, and the ARM backend
(arm_expand_vec_perm_const_1) outputs
On 15 May 2014 02:07, Jeff Law wrote:
> On 05/13/14 04:04, Zhenqiang Chen wrote:
>>
>> After reading the code in regcprop.c, I think I should reuse the
>> copyprop_hardreg_forward_1. So rewrite the patch, which is much simple
>> and should handle HAVE_cc0. But not sure we'd handle DEBUG_INSN or
>>
101 - 109 of 109 matches
Mail list logo