Hello world,
the attached patch, just an RFC so far, implements inlining
for matmul(transpose(a),b).
This implements
c = 0
do i=1, size(a,2)
do j=1, size(b,2)
do k=1, size(a,1)
c(i,j) = c(i,j) + a(k,i) * b(k,j)
end do
end do
end
On Mon, May 15, 2017 at 01:10:43PM -0700, Jerry DeLisle wrote:
>
> 2017-05-15 Jerry DeLisle
>
> PR libgfortran/80727
> * transfer.c (read_sf_internal): Remove bogus code to detect EOR.
> (read_block_form): For internal units, generate EOR if no more
> bytes left in unit
On 05/15/2017 03:51 PM, Steve Kargl wrote:
> On Mon, May 15, 2017 at 01:10:43PM -0700, Jerry DeLisle wrote:
>>
>> 2017-05-15 Jerry DeLisle
>>
>> PR libgfortran/80727
>> * transfer.c (read_sf_internal): Remove bogus code to detect EOR.
>> (read_block_form): For internal units, gene
On 05/15/2017 03:39 PM, Bernd Edlinger wrote:
On 05/15/17 03:39, Daniel Santos wrote:
On 05/14/2017 11:31 AM, Bernd Edlinger wrote:
Hi Daniel,
there is one thing I don't understand in your patch:
That is, it introduces a static value:
/* Registers who's save & restore will be managed by stubs
I've committed the trivial patch of removing the redundant
conditional.
2017-05-15 Steven G. Kargl
PR fortran/80674
* trans-stmt.c (gfc_trans_integer_select): Remove redundant condition.
Index: trans-stmt.c
===
--
If somebody writes
func (s []int) _() {}
we should report an error. Before this patch we were silently
accepting this code, because we didn't report any errors about the
receiver if the method was a sink.
This patch is unfortunately slightly complex to handle the case of
func (x int) _() {}
w
This patch cleans up the Go frontend to produce better error messages
when slicing types that can not be sliced. Previously we were always
reporting an error about indexing, even though we were slicing.
Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. Committed
to mainline.
Ian
Index: g
On 05/15/2017 04:39 AM, Prathamesh Kulkarni wrote:
Hi,
I have attached a bare-bones prototype patch that propagates malloc attribute in
ipa-pure-const. As far as I understand, from the doc a function could
be annotated
with malloc attribute if it returns a pointer to a newly allocated
memory bloc
On 05/14/2017 03:58 AM, Sylvestre Ledru wrote:
Hello,
Now that Coverity is up and running, I am trying to fix some errors.
Let's start a trivial one (same code in different branches)
S
0001-2017-05-14-Sylvestre-Ledru-sylvestre-debian.org.patch
From 50248decd02bfac52ad64b64c972750489e2ffa
Ping: Jeff, is this patch approved?
https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00547.html
On 05/08/2017 08:38 PM, Martin Sebor wrote:
On 04/28/2017 12:35 PM, Jeff Law wrote:
On 04/26/2017 11:05 AM, Martin Sebor wrote:
On 04/24/2017 03:35 PM, Jeff Law wrote:
On 04/11/2017 12:57 PM, Martin
Ian, would you mind looking at this please? A combination of my
-mcall-ms2sysv-xlogues patch with Bernd's patch is causing problems when
ix86_expand_split_stack_prologue() calls ix86_expand_call().
On 05/15/2017 06:46 PM, Daniel Santos wrote:
Rather or not m->call_ms2sysv is set determines whi
Hi,
I'd like to ping the following diagnostic-related patches that might
have slipped through the cracks:
C++ parser: Fix typos in error messages:
https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00048.html
Fix-it hints for wrong usage of 'friend' and 'auto':
https://gcc.gnu.org/ml/gcc-patches/2017
On Mon, May 15, 2017 at 10:31 PM, Andi Kleen wrote:
> "Koval, Julia" writes:
>
>> Hi,
>>
>> This patch add these missing intrinsics:
>> _xsetbv
>> _xgetbv
>
> -march=native driver support for the CPUID bit seems to be missing.
These intrinsics are under TARGET_XSAVE, and this is handled by drive
101 - 113 of 113 matches
Mail list logo
