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
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':
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
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,
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
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
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:
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) _() {}
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
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
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):
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
>
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
On 05/14/2017 09:30 AM, Sylvestre Ledru wrote:
Le 14/05/2017 à 12:40, Trevor Saunders a écrit :
On Sun, May 14, 2017 at 11:59:40AM +0200, Sylvestre Ledru wrote:
Add missing dlclose()
S
From d0926b84047f281a29dc51bbd0a4bdda01a5c63f Mon Sep 17 00:00:00 2001
From: Sylvestre
On 05/14/2017 04:40 AM, Trevor Saunders wrote:
On Sun, May 14, 2017 at 11:59:40AM +0200, Sylvestre Ledru wrote:
Add missing dlclose()
S
From d0926b84047f281a29dc51bbd0a4bdda01a5c63f Mon Sep 17 00:00:00 2001
From: Sylvestre Ledru
Date: Sun, 14 May 2017 11:28:38
On 05/14/2017 04:00 AM, Sylvestre Ledru wrote:
Add missing fclose
CID 1407987, 1407986
S
0005-2017-05-14-Sylvestre-Ledru-sylvestre-debian.org.patch
From d255827a64012fb81937d6baa8534eabecf9b735 Mon Sep 17 00:00:00 2001
From: Sylvestre Ledru
Date: Sun, 14 May 2017
Hi Carl,
On Mon, May 15, 2017 at 01:08:03PM -0700, Carl E. Love wrote:
>* config/rs6000/rs6000-c: Add support for built-in functions
>* config/rs6000/rs6000-builtin.def: Add definition for SLDW.
>* config/rs6000/altivec.h: Add defintion for vec_sldw.
>* doc/extend.texi: Update the
Hi,
On Fri, May 12, 2017 at 05:33:50PM -0400, Michael Meissner wrote:
> The problem is if the DImode, DFmode, and SFmode are allowed in Altivec
> registers before ISA 3.0, and the compiler wants to do an offsettable store.
> The compiler generates a move from an Altivec register to a traditional
On Mon, May 15, 2017 at 01:33:55PM -0700, Steve Kargl wrote:
> On Mon, May 15, 2017 at 01:10:43PM -0700, Jerry DeLisle wrote:
> > Hi all,
> >
> > Crash is a misnomer on this PR [aside: People see the backtrace and assume]
> >
> > This patch fixes the problem by correctly detecting the EOR
This is tested with powerpc-linux-gnuspe. The other subtargets are
meant to work as well, but no doubt something is still broken. I also
do not know if the port _actually_ works.
The main changes are to config.gcc; the rest is mostly filename
renames. See the cover letter for what testing is
This is also not a real patch, it is the result of this sh script:
mv gcc/common/config/powerpcspe/{rs6000,powerpcspe}-common.c
mv gcc/config/powerpcspe/driver-{rs6000,powerpcspe}.c
mv gcc/config/powerpcspe/{rs6000,powerpcspe}-builtin.def
mv gcc/config/powerpcspe/{rs6000,powerpcspe}-c.c
This is not a real patch, it is the result of this sh script:
cp -R gcc/common/config/{rs6000,powerpcspe}
cp -R gcc/config/{rs6000,powerpcspe}
Segher
Hi!
As discussed before, here is a series to split powerpcspe from the
rs6000 port. This series does not yet make any real changes to either
port: it is a copy of rs6000/ to powerpcspe/, with some renames and
some necessary changes to the port file, and slightly more involved
changes to
On Mai 15 2017, Mike Stump wrote:
> That said, a little surprising that SLE is lagging everyone else so
> hard.
DejaGnu doesn't exactly have frequent releases. Missing just one
release can easily put you more than 5 years behind.
Andreas.
--
Andreas Schwab,
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 called from
>>
This patch needs to be submitted to the libffi project.
Also, the ChangeLog needs to specify exactly what is being changed not
"Implement Go Closures". The patch clearly touches existing parts of
the files that affect more than simply Go closures.
How was this tested? libffi is used in many
/read_3.f90 -Os (test for excess errors)
=== gfortran Summary ===
# of expected passes6
# of unexpected failures6
/mnt/sgk/objx/gcc/gfortran version 8.0.0 20170515 (experimental) (GCC)
--
Steve
20170425 https://www.youtube.com/watch?v=VWUpyCsUKR4
20161221 https://www.youtube.com/watch?v=IbCHE-hONow
"Koval, Julia" writes:
> Hi,
>
> This patch add these missing intrinsics:
> _xsetbv
> _xgetbv
-march=native driver support for the CPUID bit seems to be missing.
-Andi
Please do not email my IBM Notes address with patches. Please copy
this Gmail address for patch submissions.
> * libgcc/config/rs6000/aix-unwind.h : Implements stack unwinding on AIX.
This ChangeLog entry clearly is wrong because aix-unwind.h already
implements ppc_aix_fallback_frame_state.
On 05/15/2017 04:10 AM, Paul Richard Thomas wrote:
The attached bootstraps and regtests on FC23/x86_64 - OK for trunk and
later for 7-branch?
The comment in the patch and the ChangeLog are sufficiently clear that
no further explanation is needed here.
Looks OK Paul, thanks,
Jerry
On 05/15/2017 03:38 PM, Nathan Sidwell wrote:
This cleanup patch from the modules branch fixes pr 79369, where we
would accept inlining of an already existing namespace.
missed this testcase tweak. now committed.
--
Nathan Sidwell
2017-05-15 Nathan Sidwell
PR c++/79369
Hi all,
Crash is a misnomer on this PR [aside: People see the backtrace and assume]
This patch fixes the problem by correctly detecting the EOR condition for
internal units. The previous check in read_sf_internal was wrong, relying
probably on uninitialized memory as can be seen by the still
GCC Maintainers:
This patch adds support for the various vec_bperm(), vec_mule() and
vec_mulo and vec_sldw() builtins.
The patch has been tested on powerpc64le-unknown-linux-gnu (Power 8 LE)
with no regressions.
Is the patch OK for gcc mainline?
Carl Love
On Mon, May 15, 2017 at 12:10:42PM +0100, Paul Richard Thomas wrote:
> The attached bootstraps and regtests on FC23/x86_64 - OK for trunk and
> later for 7-branch?
>
> The comment in the patch and the ChangeLog are sufficiently clear that
> no further explanation is needed here.
>
> Cheers
>
>
So how about the following then? I stayed with the catch part and added
a parameter to the warning to let the user decide on the warnings she/he
wants to get: -Wcatch-value=n.
-Wcatch-value=1 only warns for polymorphic classes that are caught by
value (to avoid slicing), -Wcatch-value=2 warns for
Hi,
I would like to ping this patch for review:
https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00775.html
Thanks,
Prathamesh
On Mon, May 15, 2017 at 12:24 PM, David Edelsohn wrote:
> On Mon, May 15, 2017 at 9:09 AM, Will Schmidt
> wrote:
>> On Sat, 2017-05-13 at 18:03 -0700, David Edelsohn wrote:
>>> On Thu, May 11, 2017 at 3:09 PM, Segher Boessenkool
>>>
This cleanup patch from the modules branch fixes pr 79369, where we
would accept inlining of an already existing namespace.
I changed push_namespace to return a count of the depth pushed, because
I also have a fix for DR 2061, where we can end up pushing more than one
namespace. That'll be
I've committed the attached patch.
2017-05-15 Steven G. Kargl
PR fortran/80752
* expr.c (gfc_generate_initializer): If type conversion fails,
check for error and return NULL.
2017-05-15 Steven G. Kargl
PR
On Mon, 15 May 2017, François Dumont wrote:
I also added some optimizations. Especially replacement of std::fill with
calls to __builtin_memset. Has anyone ever proposed to optimize std::fill in
such a way ? It would require a test on the value used to fill the range but
it might worth
On Mon, May 15, 2017 at 9:09 AM, Will Schmidt wrote:
> On Sat, 2017-05-13 at 18:03 -0700, David Edelsohn wrote:
>> On Thu, May 11, 2017 at 3:09 PM, Segher Boessenkool
>> wrote:
>> > On Thu, May 11, 2017 at 02:36:26PM -0500, Will Schmidt
On May 15, 2017, at 1:06 AM, Richard Biener wrote:
>
> Both SLE-11 and SLE-12 use dejagnu 1.4.4, so does openSUSE Leap 42.[12].
> Tumbleweed uses 1.6 so new SLE will inherit that. But I still do all
> of my testing on systems with just dejagnu 1.4.4.
So dejagnu is
Hello!
Attached patch introduces peephole2 pattern to avoid intermediate
DImode register in interunit zero-extend sequence.
However, it looks there is still slight problem with RA. Without
-mtune=intel, we have direct GR->XMM interunit moves disabled, but
pr80425-2.c testcase compiles to:
On 2017.05.15 at 16:24 +0200, Jakub Jelinek wrote:
> On Mon, May 15, 2017 at 04:13:44PM +0200, Markus Trippelsdorf wrote:
> > On 2017.05.15 at 14:02 +, Joseph Myers wrote:
> > > The xz manpage warns against blindly using -9 (for which --best is a
> > > deprecated alias) because of the
On Mon, May 15, 2017 at 02:43:43PM +0200, Richard Biener wrote:
>
> While bringing early LTO debug up-to-speed I noticed the following two
> issues. The first patch avoids useless work in
> note_variable_value_in_expr and actually makes use of the DIE we
> eventually create in
On Mon, May 15, 2017 at 04:13:44PM +0200, Markus Trippelsdorf wrote:
> On 2017.05.15 at 14:02 +, Joseph Myers wrote:
> > The xz manpage warns against blindly using -9 (for which --best is a
> > deprecated alias) because of the implications for memory requirements for
> > decompressing. If
Hi
Following what I have started on RbTree here is a patch to default
implementation of default and move constructors on std::vector.
As in _Rb_tree_impl the default allocator is not value initialized
anymore. We could add a small helper type arround the allocator to do
this value
There's a subtle bug in reorg.c's relax_delay_slots that my tester
tripped this weekend. Not sure what changed code generation wise as the
affected port built just fine last week. But it is what is is.
Assume before this code we've set TARGET_LABEL to the code_label
associated with
Hi Claudiu,
I ran the gcc testsuite with EZsim for NPS-400:
$ ./EZsim_linux_x86_64 --version
NPS-400 EZsim - Version 1.9a ( 35b02d7, Nov 3 2015, 20:14:04 )
both with and without the patch, and it did not introduce any new failures.
Best regards,
Graham.
On 15/05/17 17:48, Claudiu
On 14/05/17 09:19 +0200, Marc Glisse wrote:
Hello,
this patch adds 2 simple __glibcxx_assert in optional that match the
precondition in the comment above. I am not sure if there was a reason
the author wrote that comment instead of the assertion, but constexpr
use still seems to work.
Yes,
Hi Graham,
May I ask if you tested this with gcc's dejagnu?
Thanks,
Claudiu
On Fri, May 12, 2017 at 9:14 PM, Graham Markall
wrote:
> Since the combine pass canonicalises shift-add insns using plus and
> ashift (as opposed to plus and mult which it previously used
If config.{build,host,gcc} fails, configure currently silently
continues. This then makes it much harder than necessary to notice
you made a stupid pasto in config.gcc (and where exactly).
This patch fixes it, by terminating if one of the config.* fails.
Testing in progress (on
On Fri, May 12, 2017 at 7:57 PM, Thomas Koenig wrote:
> Am 12.05.2017 um 10:16 schrieb Janne Blomqvist:
>>
>> On Fri, May 12, 2017 at 1:14 AM, Thomas Koenig
>> wrote:
>>>
>>> Hello world,
>>>
>>> the memory allocation for the buffer in the library
Joseph's tester as well as mine tripped over this nit over the weekend.
Another argument was recently added to extract_bit_field, but the calls
in the tilegx and tilepro backends were not fixed.
This was enough to get the ports building again, including target-libgcc
and glibc.
Hi,
Saving, clearing and restoring of *callee-saved* registers when doing a
cmse_nonsecure_call is done in the __gnu_cmse_nonsecure_call libcall.
Yet, comments for cmse_nonsecure_call_clear_caller_saved claim that
it is this function that does these actions.
This commit fixes the comment to
On Sat, 2017-05-13 at 18:03 -0700, David Edelsohn wrote:
> On Thu, May 11, 2017 at 3:09 PM, Segher Boessenkool
> wrote:
> > On Thu, May 11, 2017 at 02:36:26PM -0500, Will Schmidt wrote:
> >> On Thu, 2017-05-11 at 14:15 -0500, Segher Boessenkool wrote:
> >> > Hi!
> >> >
On Thu, May 11, 2017 at 12:02 PM, Richard Biener
wrote:
> On Tue, Apr 18, 2017 at 12:54 PM, Bin Cheng wrote
>> Hi,
>> Based on vect_peeling algorithm, we know for sure that vectorized loop must
>> iterates at least once.
>> This patch sets range
On Thu, May 11, 2017 at 11:54 AM, Richard Biener
wrote:
> On Tue, Apr 18, 2017 at 12:53 PM, Bin Cheng wrote:
>> Hi,
>> Simplification of (T1)(X *+- CST) is already implemented in
>> aff_combination_expand,
>> this patch moves it to
On Thu, May 11, 2017 at 11:39 AM, Richard Biener
wrote:
> On Tue, Apr 18, 2017 at 12:53 PM, Bin Cheng wrote:
>> Hi,
>> Currently IVOPTs shares the same register pressure computation with RTL loop
>> invariant pass,
>> which doesn't work very well.
On Fri, May 12, 2017 at 9:57 AM, Thomas Koenig wrote:
> Am 12.05.2017 um 10:16 schrieb Janne Blomqvist:
>>
>> On Fri, May 12, 2017 at 1:14 AM, Thomas Koenig
>> wrote:
>>>
>>> Hello world,
>>>
>>> the memory allocation for the buffer in the library
Description:
* This patch enables the stack unwinding on AIX.
Tests:
* Fedora25/x86_64 + GCC v7.1.0 : Configure/Build: SUCCESS
- build made by means of a .spec file based on Fedora gcc-7.0.1-0.12 .spec
file
../configure --enable-bootstrap
Description:
* This patch enables FFI Go Closure on AIX.
Tests:
* Fedora25/x86_64 + GCC v7.1.0 : Configure/Build: SUCCESS
- build made by means of a .spec file based on Fedora gcc-7.0.1-0.12 .spec
file
../configure --enable-bootstrap
--enable-languages=c,c++,objc,obj-c++,fortran,go,lto
On Mon, 15 May 2017, Marek Polacek wrote:
> Thanks for pointing this out! The new version:
>
> Bootstrapped/regtested on x86_64-linux.
>
> 2017-05-15 Marek Polacek
>
> * c-common.c (c_save_expr): Remove.
> (c_common_truthvalue_conversion): Remove a call to
Description:
* This patch enables libbacktrace to handle XCOFF on AIX.
Tests:
* Fedora25/x86_64 + GCC v7.1.0 : Configure/Build: SUCCESS
- build made by means of a .spec file based on Fedora gcc-7.0.1-0.12 .spec
file
../configure --enable-bootstrap
On 05/15/2017 04:12 PM, Nathan Sidwell wrote:
> On 05/15/2017 09:06 AM, Martin Liška wrote:
>
>>> Given a blank sheet of paper, the current 'TDF_tree' dumps should really be
>>> 'TDF_gimple' dumps, so we'd have lang/ipa/gimple/rtl kinds of dumps. Such a
>>> renaming may be an unacceptable
On Fri, May 12, 2017 at 08:28:38PM +, Joseph Myers wrote:
> On Fri, 12 May 2017, Marek Polacek wrote:
>
> > In the effort of reducing early folding, we should avoid calling
> > c_fully_fold
> > blithely, except when needed for e.g. initializers. This is a teeny tiny
> > step
>
> Note
On 2017.05.15 at 14:02 +, Joseph Myers wrote:
> The xz manpage warns against blindly using -9 (for which --best is a
> deprecated alias) because of the implications for memory requirements for
> decompressing. If there's a reason it's considered appropriate here, I
> think it needs an
On 05/15/2017 09:06 AM, Martin Liška wrote:
Given a blank sheet of paper, the current 'TDF_tree' dumps should really be
'TDF_gimple' dumps, so we'd have lang/ipa/gimple/rtl kinds of dumps. Such a
renaming may be an unacceptable amount of churn though.
Well, I would prefer to introduce new
Description:
* This patch enables libiberty to read AIX XCOFF.
Tests:
* Fedora25/x86_64 + GCC v7.1.0 : Configure/Build: SUCCESS
- build made by means of a .spec file based on Fedora gcc-7.0.1-0.12 .spec
file
../configure --enable-bootstrap
The xz manpage warns against blindly using -9 (for which --best is a
deprecated alias) because of the implications for memory requirements for
decompressing. If there's a reason it's considered appropriate here, I
think it needs an explanatory comment.
--
Joseph S. Myers
Nico Josuttis pointed out that the members were in the wrong order. I
also found that set::insert__return_type::position was using
_Rb_tree_iterator not _Rb_tree_const_iterator as it should have
been.
Finally, with complete structured bindings support in the FE we don't
need the tuple_size and
On 05/15/2017 05:46 AM, Joseph Myers wrote:
The extra argument to extract_bit_field breaks builds for tilegx-linux-gnu
and tilepro-linux-gnu (as shown by my glibc bot); there are calls in those
back ends which haven't been updated.
I've got patches for the tile backends that I'll push today.
On 05/15/2017 02:24 PM, Nathan Sidwell wrote:
> On 05/15/2017 08:04 AM, Martin Liška wrote:
>> On 05/15/2017 01:33 PM, Nathan Sidwell wrote:
>
>>> 1) The TDF_UID and TDF_NOUID options seem to be inverses of each other.
>>> Can't we just ditch the latter?
>>
>> One is used to paper over UIDs in
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the Swedish team of translators. The file is available at:
http://translationproject.org/latest/gcc/sv.po
(This file, 'gcc-7.1.0.sv.po', has
While bringing early LTO debug up-to-speed I noticed the following two
issues. The first patch avoids useless work in
note_variable_value_in_expr and actually makes use of the DIE we
eventually create in resolve_variable_value_in_expr.
The second avoids generating a DW_OP_GNU_variable_value
On 05/15/2017 08:04 AM, Martin Liška wrote:
On 05/15/2017 01:33 PM, Nathan Sidwell wrote:
1) The TDF_UID and TDF_NOUID options seem to be inverses of each other. Can't
we just ditch the latter?
One is used to paper over UIDs in order to preserve -fdebug-compare (I
believe). And the second
On 05/15/2017 01:18 PM, Nathan Sidwell wrote:
> On 05/15/2017 05:39 AM, Martin Liška wrote:
>> Thanks Martin for feedback! After I spent quite some time with fiddling with
>> the options, I'm not convinced we should convert options to more hierarchical
>
> I'll respond to Martin's email properly
On Mon, May 15, 2017 at 12:17 PM, Martin Liška wrote:
> Hello.
>
> There are situations where local variables (defined in a switch scope) do
> not belong to any BIND_EXPR. Thus, we ICE due to gcc_assert
> (gimplify_ctxp->live_switch_vars->elements () == 0);
>
> Is there any
On 05/15/2017 01:33 PM, Nathan Sidwell wrote:
> Martin,
> thanks for the write up.
>
> On 05/15/2017 05:39 AM, Martin Liška wrote:
>> Thanks Martin for feedback! After I spent quite some time with fiddling with
>> > the options, I'm not convinced we should convert options to more
>
On Mon, May 15, 2017 at 11:52 AM, Martin Liška wrote:
> Hello.
>
> This is fix for old issues which can be still exposed.
> Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
>
> Ready to be installed?
+ if (output_file != NULL && output_file[0] == '\0')
Hi!
On Mon, 15 May 2017 08:52:39 +0200, I wrote:
> On Tue, 28 Feb 2017 18:43:36 +0100, I wrote:
> > The 2.5 versions of the OpenACC standard added a new chapter "Profiling
> > Interface". In r245784, I committed incomplete support to
> > gomp-4_0-branch. I plan to continue working on this, but
Hi!
Given that on gomp-4_0-branch we're now implementing most of what has
been added/changed in OpenACC 2.5, it seemed to make sense to apply the
following to gomp-4_0-branch in r248057:
commit 72ae911aeab1e0664db5737f339fcd81cceff287
Author: tschwinge
The extra argument to extract_bit_field breaks builds for tilegx-linux-gnu
and tilepro-linux-gnu (as shown by my glibc bot); there are calls in those
back ends which haven't been updated.
--
Joseph S. Myers
jos...@codesourcery.com
Martin,
thanks for the write up.
On 05/15/2017 05:39 AM, Martin Liška wrote:
Thanks Martin for feedback! After I spent quite some time with fiddling with > the options, I'm not convinced we should convert options to more
hierarchical> structure. There's description:
1) -fopt-info is used to
Hi Richard,
Thanks! committed with all the comments resolved.
Regards,
Renlin
On 02/05/17 13:53, Richard Earnshaw (lists) wrote:
On 01/12/16 15:39, Renlin Li wrote:
Hi all,
This patch refactors the code used in call, call_value, sibcall,
sibcall_value expanders.
Before the change, the
On 05/15/2017 05:39 AM, Martin Liška wrote:
Thanks Martin for feedback! After I spent quite some time with fiddling with
the options, I'm not convinced we should convert options to more hierarchical
I'll respond to Martin's email properly separates, but while we're on
dump redesign, here's a
The attached bootstraps and regtests on FC23/x86_64 - OK for trunk and
later for 7-branch?
The comment in the patch and the ChangeLog are sufficiently clear that
no further explanation is needed here.
Cheers
Paul
2017-05-15 Paul Thomas
PR fortran/80554
* decl.c
On 12/05/17 21:33 +0300, Ville Voutilainen wrote:
libstdc++-v3/
Implement new C++ intrinsics __is_assignable and __is_constructible.
* include/std/type_traits (__do_is_static_castable_impl): Remove.
(__is_static_castable_impl, __is_static_castable_safe): Likewise.
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 block (uninitialized or zeroed) and the pointer does not
Resending the message to list, Sorry I hadn't noticed somewhere along the line
it was dropped..
Hi All,
I believe Joseph had no more comments for the patch.
Any other comments or OK for trunk?
Regards,
Tamar
From: Tamar Christina
Sent: Tuesday, May 2,
Hello.
There are situations where local variables (defined in a switch scope) do
not belong to any BIND_EXPR. Thus, we ICE due to gcc_assert
(gimplify_ctxp->live_switch_vars->elements () == 0);
Is there any better solution how we can catch these variables?
Suggested patch can bootstrap on
Hello.
This is fix for old issues which can be still exposed.
Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
Ready to be installed?
Martin
>From 0cbecc941d9b53de8235d5147ee3891d57af5f49 Mon Sep 17 00:00:00 2001
From: marxin
Date: Wed, 3 May 2017
On Fri, May 12, 2017 at 09:48:28PM +0200, Jakub Jelinek wrote:
> On Fri, May 12, 2017 at 09:37:27PM +0200, Marek Polacek wrote:
> > @@ -565,6 +564,25 @@ c_fully_fold_internal (tree expr, bool in_init, bool
> > *maybe_const_operands,
> > appropriate in any particular case. */
> >
Hello.
Thanks Martin for feedback! After I spent quite some time with fiddling with
the options, I'm not convinced we should convert options to more hierarchical
structure. There's description:
1) -fopt-info is used to dump optimization options. One can pick both verbosity
(note, optimization,
Hi,
Reg-tested now on arm-none-linux-gnueabihf as well and no regressions.
Ok for trunk?
Tamar
From: Ramana Radhakrishnan
Sent: Monday, May 15, 2017 9:40:40 AM
To: Tamar Christina
Cc: GCC Patches; nd; Kyrylo Tkachov; Richard
Tested on x86_64-suse-linux, applied on the mainline.
2017-05-15 Pierre-Marie de Rodat
* gcc-interface/utils.c (can_materialize_object_renaming_p):
Synchronize with GNAT's Exp_Dbug.Debug_Renaming_Declaration:
process Original_Node instead of
Hi Tamar,
On 02/05/17 15:46, Tamar Christina wrote:
Hi All,
I'm taking this one over from Matthew, I think it slipped through the cracks
before.
Since it still applies cleanly on trunk I'm just pinging it.
Ok for trunk?
Sorry for missing this.
For the record you are referring to the
Tested on x86_64-suse-linux, applied on the mainline.
2017-05-15 Eric Botcazou
* gcc-interface/trans.c (return_value_ok_for_nrv_p): Only apply the
addressability check in the constrained case.
--
Eric BotcazouIndex: gcc-interface/trans.c
On Tue, May 2, 2017 at 4:37 PM, Tamar Christina wrote:
> Hi All,
>
> This patch adjusts the cost model for Cortex-A53 to increase the costs of
> an integer division. The reason for this is that we want to always expand
> the division to a multiply when doing a division by
On Mon, May 15, 2017 at 9:27 AM, Richard Biener
wrote:
> On Fri, May 12, 2017 at 7:51 PM, Bernd Schmidt wrote:
>> If you look at certain testcases like the one for PR78972, you'll find that
>> the code generated by TER is maximally pessimal in
1 - 100 of 114 matches
Mail list logo