On Nov 14, 2016, at 12:31 PM, Ramana Radhakrishnan
wrote:
>
> https://sourceware.org/ml/newlib/2015/msg00653.html
I think that patch is wrong. It is wrong to warn on a system where an empty
body is correct. It is wrong to warn when something more than nothing needs to
be done. In short, it
On 14 November 2016 at 00:43, Jonathan Wakely wrote:
>> Oh, they aren't actually constexpr in your patch, so non-const, and so
>> don't get internal linkage. But they *should* be constexpr, please add
>> that to all three, and add inline to the two variable templates.
> P.S. OK with those changes.
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/make_signed tests seem broken. That's not caused by
any of my patc
On 14 November 2016 at 04:03, Jonathan Wakely wrote:
> OK, thanks.
This is what I committed after a full testsuite run on Linux-PPC64.
2016-11-14 Ville Voutilainen
Implement P0513R0, Poisoning the Hash.
* include/bits/functional_hash.h (__poison_hash): New.
* include/bits/unique
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 */
+ c_dim1 = rystride;
+ c_offset = 1 + c_dim1;
Regarding options for matmul: It is po
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 various commits
and now just verifies that ssa_var is indeed a SSA_NAME and not a
On Fri, Nov 11, 2016 at 6:02 AM, Rainer Orth
wrote:
>
>> This patch to the Go frontend and libgo copies the signal code from
>> the Go 1.7 runtime.
>>
>> This adds a little shell script to auto-generate runtime.sigtable from
>> the known signal names.
>>
>> This forces the main package to always i
On 11/14/2016 02:55 AM, James Greenhalgh wrote:
On Fri, Nov 11, 2016 at 09:42:32PM -0700, Sandra Loosemore wrote:
On 11/11/2016 08:37 AM, James Greenhalgh wrote:
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index f133b3a..75ff8ec 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke
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 checked and rejected when missing.
Otherwise the demangler will cras
This patch adds built-in function support for the new setb, cmprb, and
cmpeqb Power9 instructions.
The patch has been bootstrapped and tested on
powerpc64le-unknown-linux and powerpc-unknown-linux (big-endian, with
both -m32 and -m64 target options) with no regresions.
Is this ok for the trunk?
On Mon, Nov 14, 2016 at 05:56:49AM +0100, Michael Matz wrote:
> With this patch there are now no regressions on x86-64-linux (bootstrapped
> with all languages+ada). Okay for trunk?
I build cross-compilers for this for a whole bunch of archs, and built
Linux with that, to see what effect this ha
On Mon, Nov 14, 2016 at 11:09:19AM +0100, Richard Biener wrote:
> On Sat, Nov 12, 2016 at 9:31 AM, Segher Boessenkool
> wrote:
> > 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 register
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.
Apparently the target mapping wants to use 't' in a way that doesn't
actu
Some fixes for bit-field and decltype handling, and address comparison
in constant expressions.
Tested x86_64-pc-linux-gnu, applied to trunk.
On Mon, Nov 14, 2016 at 10:16 AM, Jason Merrill wrote:
> On Mon, Nov 14, 2016 at 9:51 AM, Jakub Jelinek wrote:
>> On Sun, Nov 13, 2016 at 11:53:10PM -050
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_offset, b_dim1, b_offset, c_dim1, c_offset, i
101 - 115 of 115 matches
Mail list logo