Richard Sandiford writes:
> Jakub Jelinek writes:
>> Hi!
>>
>> Note the intent of the pass is to handle the most common cases, it is fine
>> if some cases that aren't common aren't handled, it is all about the extra
>> complexity vs. how much it helps on real-world code.
>
> OK.
>
>> On Sun, May
On Wed, May 17, 2017 at 4:45 AM, Hans-Peter Nilsson wrote:
>> But yes, we definitely should document the final canonical ordering.
>
> Is that about to also happen?
>
> I foresee in another half-a-dozen years, and *this* iteration is
> forgotten, someone bothered enough to argue eloquently coming
Hi,
The test declares malloc with an unsigned long parameter. This causes
a warning for avr, as it's size_t is only unsigned int.
Fixed by typdef'ing __SIZE_TYPE__ to size_t and using it in the malloc
function's declaration.
Committed as obvious.
Regards
Senthil
gcc/testsuite/ChangeL
On 15/05/17 22:51, Segher Boessenkool wrote:
-- This uses powerpc-*-rtems*spe*; do we want powerpcspe-*-rtems*
instead? Or both?
I guess it will be powerpcspe-*-rtems*, but we have to fix our build
system in this case. Don't worry about RTEMS.
--
Sebastian Huber, embedded brains GmbH
A
Hi all,
When I first looked at this I thought the minor front end bobble was the
problem. That turns out to be unrelated but needed to be fixed in trans-io.c
The actual problem was that when I moved the last_char to the unit structure,
needed for DTIO, the value saved there persists across I/
On 2017.05.16 at 19:16 -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> When running creduce on an ICE substantial amounts of the total
> CPU time go to backtrace_qsort() (sorting dwarf of the compiler) for
> printing the backtrace of the ICE. When running a reduction we don't need the
> backtrace
On Tue, May 16, 2017 at 7:16 PM, Andi Kleen wrote:
> From: Andi Kleen
>
> When running creduce on an ICE substantial amounts of the total
> CPU time go to backtrace_qsort() (sorting dwarf of the compiler) for
> printing the backtrace of the ICE. When running a reduction we don't need the
> backtr
On Tue, May 16, 2017 at 7:16 PM, Andi Kleen wrote:
> From: Andi Kleen
>
> When running creduce on an ICE substantial amounts of the total
> CPU time go to backtrace_qsort() (sorting dwarf of the compiler) for
> printing the backtrace of the ICE. When running a reduction we don't need the
> backtr
On Fri, 12 May 2017, Jeff Law wrote:
> On 05/11/2017 03:29 PM, Hans-Peter Nilsson wrote:
> > The canonical order of insns affecting condition-codes has been
> > discussed in the past too.
> >
> > I was then arguing that the compare should go last, i.e.
> > (parallel [(set (reg) (op...))
> >
From: Andi Kleen
A tree type dump currently doesn't print the attributes. Since we have
so many now and they do many interesting things dumping them can be
useful. So dump them by default for tree type dumps.
Passes bootstrap and testing on x86_64-linux.
gcc/:
2017-05-16 Andi Kleen
From: Andi Kleen
When running creduce on an ICE substantial amounts of the total
CPU time go to backtrace_qsort() (sorting dwarf of the compiler) for
printing the backtrace of the ICE. When running a reduction we don't need the
backtrace. So add a -dB option to turn it off, and make reduction
a b
Hi:
commited as r248137.
Thanks,
paul.
On Wed, May 17, 2017 at 2:46 AM, Toma Tabacu wrote:
> From: Jeff Law
>> On 05/16/2017 10:01 AM, Toma Tabacu wrote:
>>> Hello Paul,
>>>
>>> You're seeing this problem because mips.exp can't handle -O* in dg-options.
>>> The other tests in gcc.target/mips us
From: Andi Kleen
When a verification check fails it is useful to dump the current
function to the dump file, so it's easier to figure out what
actually went wrong.
Add function dumps for gimple or SSA verification failures.
Suggested by Jakub.
Passes bootstrap and testing on x86_64-linux
gcc/
On 05/16/2017 02:52 PM, Bernd Edlinger wrote:
I think I solved the problem with -fsplit-stack, I am not sure
if ix86_static_chain_on_stack might change after reload due to
final.c possibly calling targetm.calls.static_chain, but if that
is the case, that is an already pre-existing problem.
The g
On 05/16/2017 04:48 PM, Pedro Alves wrote:
On 05/16/2017 08:41 PM, Jason Merrill wrote:
I agree that it makes sense to
check for a trivial assignment operator specifically. I guess we want
a slightly stronger "trivially copyable" that also requires a
non-deleted assignment operator.
It seems
The AIX Assembler inserts the DWARF section lengths itself.
dwarf2out.c previously has been modified to not emit the length on
AIX. All well and good until GCC emits a label that it believes
references the start of a DWARF section, but actually references an
address _after_ the section length inse
On 05/16/2017 08:41 PM, Jason Merrill wrote:
> I agree that it makes sense to
> check for a trivial assignment operator specifically. I guess we want
> a slightly stronger "trivially copyable" that also requires a
> non-deleted assignment operator.
>
> It seems to me that the relevant tests are:
The test case in PR80775 exposes a problem in handling two separate
case labels that lead to the same block that contains a call to
__builtin_unreachable(). The current code handles the first label
and deletes the associated edge/block, but trips up when we see the
second case label that now poin
On Tue, 16 May 2017, Cesar Philippidis wrote:
> Arguably, I probably should have split the backport into a separate
> patch. However, I think this only impacts libgomp. And I was tempted to
> just to copy the complete texinfo.tex file from texinfo 6.3, like it was
> last done in 2012. However, I w
On 05/16/2017 01:41 PM, Jason Merrill wrote:
On Thu, May 11, 2017 at 12:23 PM, Martin Sebor wrote:
The challenge with using memcpy or memset with class types is
figuring out if it's being called to copy-construct a new object
or assign a new value to an existing one. In general it's not
possib
On Tue, 16 May 2017, François Dumont wrote:
What is match.pd ?
It is a file in gcc where we describe simple pattern-matching
optimizations. In this case, IIRC, the missing transformations were
* ptr + n == ptr + 1 --> n == 1 (we already do it if 1 is replaced by a
variable or 0)
* ((n/8)+1)
On 05/16/2017 12:19 PM, Ian Lance Taylor wrote:
On Mon, May 15, 2017 at 10:00 PM, Daniel Santos wrote:
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_c
This patch does two things:
1. Updates the libgomp documentation to reflect the recent OpenACC 2.5
changes.
2. Backports a texinfo patch to wrap the title of the libgomp manual
in the pdf. Without it, part of the title would get truncated out
of the page.
For the most part, the gom
On 05/16/17 21:52, Bernd Edlinger wrote:
> The calls_eh_return and ix86_static_chain_on_stack may become
> known at a later time, but after reload it should not change any more.
> To be sure, I added an assertion at ix86_static_chain, which the
> regression test did not trigger, neither with -m64 n
On 15/05/2017 21:31, Marc Glisse wrote:
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
Hi Jerry and Steve,
Thanks for taking a peek - committed as revision 248129.
I'll commit to 7-branch in a couple of weeks.
Cheers
Paul
On 15 May 2017 at 21:29, Jerry DeLisle wrote:
> On 05/15/2017 04:10 AM, Paul Richard Thomas wrote:
>>
>> The attached bootstraps and regtests on FC23/x86_64 -
On 05/16/17 19:19, Ian Lance Taylor wrote:
> On Mon, May 15, 2017 at 10:00 PM, Daniel Santos
> wrote:
>>
>> 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
On 05/16/2017 01:20 PM, Tim Song wrote:
On Tue, May 16, 2017 at 2:50 PM, Martin Sebor wrote:
I'm not sure I understand why the ovl_iterator assignment needs
to be provided but if it does, not also defining one on the derived
class will call the base and return a reference to the base, making
th
On Thu, May 11, 2017 at 12:23 PM, Martin Sebor wrote:
> The challenge with using memcpy or memset with class types is
> figuring out if it's being called to copy-construct a new object
> or assign a new value to an existing one. In general it's not
> possible to tell so the conservative assumptio
Sorry for not getting back to your original post Paolo. I haven't been
picking up mails for a while.
On 2017-05-01 16:56, Jason Merrill wrote:
On Thu, Apr 27, 2017 at 2:02 PM, Paolo Carlini
wrote:
On 26/04/2017 12:32, Paolo Carlini wrote:
in 2013 (2013-09-16) Adam added two slightly obscur
On 05/16/2017 01:05 PM, Nathan Sidwell wrote:
Martin,
Thanks for taking a look. There's a whole patch series I hope to land
over the next couple of weeks. Things may be clearer at that point.
Just a couple of suggestions, It looks like the classes model
the concept of Forward Iterator. May
On 05/16/2017 03:27 PM, Tim Song wrote:
https://en.wikibooks.org/wiki/More_C%2B%2B_Idioms/Safe_bool
Oh, I see. I'm not going to stop someone adding it, but for me, it's
quite far down my priority list.
I suspect that we don't want adding two ovl_iterators together to compile.
Why would
On Tue, May 16, 2017 at 3:24 PM, Nathan Sidwell wrote:
> On 05/16/2017 03:20 PM, Tim Song wrote:
>
>> Also, operator bool() seems suspect. Consider the safe bool idiom?
>
> ?
https://en.wikibooks.org/wiki/More_C%2B%2B_Idioms/Safe_bool
I suspect that we don't want adding two ovl_iterators together
On 05/16/2017 03:20 PM, Tim Song wrote:
Also, operator bool() seems suspect. Consider the safe bool idiom?
?
And is it intended that tree implicitly converts to both iterators, or
should those constructors be explicit?
Maybe. Not caused a problem in practice -- never passing iterators
aro
This patch breaks out the shadowed variable checking from pushdecl to a
worker function. pushdecl was too big.
nathan
--
Nathan Sidwell
2017-05-16 Nathan Sidwell
* name-lookup.c (check_local_shadow): New, broke out of ...
(pushdecl_maybe_friend_1): ... here. Call it.
Index: name-lookup.
On Tue, May 16, 2017 at 2:50 PM, Martin Sebor wrote:
> I'm not sure I understand why the ovl_iterator assignment needs
> to be provided but if it does, not also defining one on the derived
> class will call the base and return a reference to the base, making
> the result no longer suitable where t
On 05/16/2017 03:05 PM, Nathan Sidwell wrote:
PS More descriptive names would be a nice as well (neither
lkp_ nor ovl_ is intuitive enough at first glance.) Maybe
lookup_iter and overload_iter?
Works for me -- I just noticed we had things like vec_iterator already,
and continued that naming.
On May 16, 2017, at 5:16 AM, Jonathan Wakely wrote:
> The change I care about in 1.5.3
So, we haven't talked much about the version people want most. If we update,
might as well get something that more people care about. 1.5.3 is in ubuntu
LTS 16.04 and Fedora 24, so it's been around awhile.
Martin,
Thanks for taking a look. There's a whole patch series I hope to land
over the next couple of weeks. Things may be clearer at that point.
Just a couple of suggestions, It looks like the classes model
the concept of Forward Iterator. May I suggest to make them
model it more closely
On 05/16/2017 08:50 AM, Nathan Sidwell wrote:
This patch implements new iterators for OVERLOADs. There are two
iterators:
ovl_iterator for a plain iterator, that held on a binding
lkp_iterator for the overload set returned by lookup.
To use them simply:
for (lkp_iterator iter (INIT); iter; ++
From: Jeff Law
> On 05/16/2017 10:01 AM, Toma Tabacu wrote:
>> Hello Paul,
>>
>> You're seeing this problem because mips.exp can't handle -O* in dg-options.
>> The other tests in gcc.target/mips use a dg-skip-if to skip for -O0 and -O1
>> instead of having -O2 in dg-options.
>> This is supposed to
On Fri, May 12, 2017 at 2:33 PM, Ville Voutilainen
wrote:
> On 12 May 2017 at 14:15, Ville Voutilainen
> wrote:
>> On 12 May 2017 at 14:06, Daniel Krügler wrote:
>>> Your description sounds remotely similar to me to the current problem
>>> of __is_trivially_constructible intrinsic, which seems
On Fri, May 12, 2017 at 6:09 AM, Marek Polacek wrote:
> On Fri, May 12, 2017 at 09:32:48AM +0200, Richard Biener wrote:
>> On Thu, May 11, 2017 at 3:49 PM, Marek Polacek wrote:
>> > I had an interesting time coming to grips with these two PRs. But it
>> > essentially comes down to the fold call
On 16.05.2017 05:35, Bernhard Reutner-Fischer wrote:
> On 16 May 2017 at 14:16, Jonathan Wakely wrote:
>> On 16 May 2017 at 13:13, Bernhard Reutner-Fischer wrote:
>>> 1.5.0 wouldn't buy us anything as the "libdirs" handling is only in 1.5.2
>>> and later.
>>
>> Ah I missed that in the earlier dis
This patch to do_class_deduction notices that we currently add some
candidates and them immediately elide them from the set. Why not just
not add them?
Adding to the overload set uses a new lookup_add function, which in turn
uses a new ovl_make. A couple of new OVL_foo flags appear, which wi
On Tue, May 9, 2017 at 8:05 AM, Nathan Sidwell wrote:
> I'm also prepared to remove the -fdump-translation-unit dumper, which is a
> completely inscrutable c++ only dump, that I think is well past its
> best-before date. (Jason?)
I think that's left over from previous modulesish work by Gaby and
OK.
On Fri, May 5, 2017 at 6:50 PM, David Malcolm wrote:
> On Mon, 2017-05-01 at 14:43 -0400, Jason Merrill wrote:
>> On Thu, Apr 27, 2017 at 7:23 AM, Nathan Sidwell
>> wrote:
>> > On 04/26/2017 12:34 PM, David Malcolm wrote:
>> >
>> > > Thanks - yes; that gives information on the const vs non-c
This patch converts more pieces to use {ovl,lkp}_iterator. Also a few
places OVL_FIRST should now be being used.
I don't think anything here is particularly obscure.
nathan
--
Nathan Sidwell
2017-05-16 Nathan Sidwell
* call.c (build_user_type_conversion_1): Use OVL_FIRST.
(print_error_fo
On Mon, May 15, 2017 at 10:00 PM, Daniel Santos wrote:
>
> 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().
I don't have a lot of context here.
On 05/16/2017 10:50 AM, Jason Merrill wrote:
The change to cxx_incomplete_type_diagnostic seems wrong; the member
might be a data member.
I couldn't get there with a non-overload, but then I couldn't convince
myself there was no other path. It's hardly a critical path, so reverted.
--
Natha
On 05/16/2017 10:01 AM, Toma Tabacu wrote:
> Hello Paul,
>
> You're seeing this problem because mips.exp can't handle -O* in dg-options.
> The other tests in gcc.target/mips use a dg-skip-if to skip for -O0 and -O1
> instead of having -O2 in dg-options.
> This is supposed to ensure that the tests
I've fixed the test, there was a typo in the regexpr that made it fail only
when the register allocator happens to pick a register other than d0.
Commited as r 248117.
> -Original Message-
> From: Christophe Lyon [mailto:christophe.l...@linaro.org]
> Sent: 16 May 2017 14:21
> To: Tamar Ch
Hello Paul,
You're seeing this problem because mips.exp can't handle -O* in dg-options.
The other tests in gcc.target/mips use a dg-skip-if to skip for -O0 and -O1
instead of having -O2 in dg-options.
This is supposed to ensure that the tests are run for as many optimization
levels as possible.
Hi All,
This fixes two assembler scan tests for ARM.
The typo in the test made it fail if anything
but d0 is used.
Committed as r 248117 under the GCC obvious rule.
gcc/testsuite/
2017-05-16 Tamar Christina
* gcc.target/arm/armv8_2-fp16-neon-1.c (vceqz): Fix regex.
* gcc.targ
This patch breaks apart the creation of the pass manager from
gcc::context's ctor. This will allow us to register additional dumps
between the dumpfile manager creation and the pass manager. As I
described in https://gcc.gnu.org/ml/gcc-patches/2017-05/msg01164.html
when I tried to do this for
On Tue, May 16, 2017 at 10:44 AM, REIX, Tony wrote:
> Hi David,
>
> We'll submit the patch to the libffi project asap.
>
> We have tested this patch on AIX 6.1 with libffi (master from github) in
> 32bit and 64bit with same results (same exact failures) when testing with and
> without our patch,
On 05/16/2017 03:34 AM, Bernd Edlinger wrote:
It would be good to have test cases for each of the not-supported warnings that
can happen, so far I only managed to get a test case for -fsplit-stack.
Yes, I'm inclined to agree. I'll try to get this done today or
tomorrow. I've also put in a li
Hello!
2017-05-16 Uros Bizjak
* config/i386.i386.md (*movsi_internal): Split (?rm,*y) alternative
to (?r,*Yn) and (?m,*y) alternatives, and (?*y,rm) to (?*Ym,r)
and (?*y,m). Update insn attributes.
Bootstrapped and regression tested on x86_64-linux-gnu {,-m32}.
Committed to main
On 05/16/2017 10:50 AM, Jason Merrill wrote:
The change to cxx_incomplete_type_diagnostic seems wrong; the member
might be a data member.
I had convinced myself that at that point it couldn't be. Will take
another look though.
Anyway, thanks for the review!
nathan
--
Nathan Sidwell
On 05/16/2017 03:48 PM, Richard Biener wrote:
> On Fri, May 12, 2017 at 3:00 PM, Martin Liška wrote:
>> Second part changes 'int flags' to a new typedef.
>> All corresponding interfaces have been changed.
>>
>> Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
>>
>> Ready
The change to cxx_incomplete_type_diagnostic seems wrong; the member
might be a data member.
Jason
This patch implements new iterators for OVERLOADs. There are two iterators:
ovl_iterator for a plain iterator, that held on a binding
lkp_iterator for the overload set returned by lookup.
To use them simply:
for (lkp_iterator iter (INIT); iter; ++iter)
{ tree fn = *iter;
... }
Curre
Hi David,
We'll submit the patch to the libffi project asap.
We have tested this patch on AIX 6.1 with libffi (master from github) in 32bit
and 64bit with same results (same exact failures) when testing with and without
our patch, using libffi testsuite.
Without patch:
=== libf
Hi Christoph,
> > Thanks, bootstrapped and regtested now on arm-none-linux-gnueabihf
> and no issues.
> > I'll go ahead and commit then.
> >
>
> One of the new tests fails on arm-none-linux-gnueabi (non-hf) targets:
> FAIL:gcc.target/arm/armv8_2-fp16-neon-2.c scan-assembler-times
> vceq\\.f16
On 16/05/17 14:40 +0100, Jonathan Wakely wrote:
This is a partial implementation of ,
see the commented-out lines in the testcase for the missing pieces.
I'll be opening a PR to get the needed front-end support complete it.
That's https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80780
+struct S
On Tue, May 16, 2017 at 9:50 AM, REIX, Tony wrote:
> Tests:
>
> The change has been tested in 32bit and 64bit on AIX 6.1, 7.1 & 7.2 by using
> the libbacktrace (with XCOFF support) within a signal handler context (we
> used a specific back.c program).
> And it has been tested with Go tests on AI
On Fri, May 12, 2017 at 3:04 PM, Martin Liška wrote:
> Third part removes TDF_* flags mentioned in the subject. These flags are used
> to enable all passes of specific type and Nathan has recently separated these
> by a new pair of macros. I hope moving these to a separate enum will help
> even m
There's one another patch that merges some TDF_* flags that have
very similar meaning and do not influence test-suite, because
nobody is using them for scanning.
Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
Ready to be installed?
Martin
>From d75cc6896b1041042c4aea31
Tests:
The change has been tested in 32bit and 64bit on AIX 6.1, 7.1 & 7.2 by using
the libbacktrace (with XCOFF support) within a signal handler context (we used
a specific back.c program).
And it has been tested with Go tests on AIX for sure (recover tests on SIGSEGV
do not work without this
On Fri, May 12, 2017 at 3:00 PM, Martin Liška wrote:
> Second part changes 'int flags' to a new typedef.
> All corresponding interfaces have been changed.
>
> Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
>
> Ready to be installed?
@@ -113,6 +114,14 @@ enum tree_dump_
On Fri, May 12, 2017 at 2:57 PM, Martin Liška wrote:
> Hello.
>
> After fiddling with that, I decided to come up with reworked first part
> of the patch and eventual translation to a more hierarchical structure
> is subject for discussion.
>
> This first patch adds default for couple of dump funct
On Mon, May 15, 2017 at 4:21 PM, Martin Liška wrote:
> 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 o
Martin L. asked me to have a look at this ICE with ASAN. This is an ICE with a
compound literal in a switch. A hash map gimplify_ctxp->live_switch_vars is
filled when processing DECL_EXPRs with their DECL_EXPR_DECLs. Such decls should
then be removed from the hash map when gimplifying a BIND_EXP
This is a partial implementation of ,
see the commented-out lines in the testcase for the missing pieces.
I'll be opening a PR to get the needed front-end support complete it.
* configure: Regenerate.
* doc/xml/manual/status_cxx2017.xml: Update status table.
* doc/html/*:
Hi,
On 16 May 2017 at 10:48, Tamar Christina wrote:
> Hi Kyrill,
>>
>> Sorry for missing this.
>> For the record you are referring to the patch at:
>> https://gcc.gnu.org/ml/gcc-patches/2016-09/msg01700.html
>>
>> This is ok and in line with what we do for the f32 intrinsics.
>> My only concern w
My reworking of overload management will be introducing
overloads-of-overloads as lookup results.
This patch introduces OVL_FIRST to get the first function of a lookup
set, and OVL_NAME to get the DECL_NAME of that (a useful accessor). In
many case we were unnecessarily using get_fns or get_f
On 11/05/17 15:19 +0100, Jonathan Wakely wrote:
std::make_shared didn't support embedding the object within the
shared_ptr bookkeeping structure when -fno-rtti was used. This was
because the trick I use for getting the address of the embedded
object relied on typeid, so without RTTI it just creat
Some random cleanups with get_fns & get_first_fn from the modules
branch. I started cleaning up these and is_overloaded_fn & friends, but
that turned into a bit of a rat hole. There's certainly more mileage to
be gotten though.
These cleanups are generally callers unnecessarily stripping bit
Hi Tom,
sorry for chiming in so very late: I've been on vacation and sick in
between...
> On 04/24/2017 05:20 PM, David Malcolm wrote:
>> On Sat, 2017-04-22 at 19:49 +0200, Tom de Vries wrote:
>>> Hi,
>>>
>>> there are currently two types of line number supported in
>>> dg-{error,warning,message
On 16/05/17 12:48 +0100, Jonathan Wakely wrote:
On 11/05/17 22:31 +0200, François Dumont wrote:
On 10/05/2017 22:44, François Dumont wrote:
On 10/05/2017 11:28, Jonathan Wakely wrote:
On 10/05/17 11:15 +0200, Paolo Carlini wrote:
Hi,
On 10/05/2017 11:12, Jonathan Wakely wrote:
Looks good to
This patch for gomp-4_0-branch implements OpenACC 2.5 reference counting
of mappings, the finalize clause of the exit data directive, and the
corresponding API routines.
Tested without regressions, committed to gomp-4_0-branch.
Chung-Lin
2017-05-16 Chung-Lin Tang
gcc/c/
* c-p
On 16 May 2017 at 14:16, Jonathan Wakely wrote:
> On 16 May 2017 at 13:13, Bernhard Reutner-Fischer wrote:
>> 1.5.0 wouldn't buy us anything as the "libdirs" handling is only in 1.5.2
>> and later.
>
> Ah I missed that in the earlier discussion.
>
> The change I care about in 1.5.3 is
> http://gi
On 16 May 2017 at 13:13, Bernhard Reutner-Fischer wrote:
> 1.5.0 wouldn't buy us anything as the "libdirs" handling is only in 1.5.2 and
> later.
Ah I missed that in the earlier discussion.
The change I care about in 1.5.3 is
http://git.savannah.gnu.org/gitweb/?p=dejagnu.git;a=commit;h=5256bd823
On 16 May 2017 11:54:18 CEST, Jonathan Wakely wrote:
>On 13 May 2017 at 11:38, Jakub Jelinek wrote:
>> On Sat, May 13, 2017 at 12:24:12PM +0200, Bernhard Reutner-Fischer
>wrote:
>>> I guess neither redhat
>>> (https://access.redhat.com/downloads/content/dejagnu/ redirects to a
>>> login page but t
On 11/05/17 22:31 +0200, François Dumont wrote:
On 10/05/2017 22:44, François Dumont wrote:
On 10/05/2017 11:28, Jonathan Wakely wrote:
On 10/05/17 11:15 +0200, Paolo Carlini wrote:
Hi,
On 10/05/2017 11:12, Jonathan Wakely wrote:
Looks good to me. Paolo, what do you think about bumping the v
On Mon, 15 May 2017, 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
>
Currently, namespace_decls have no record of how deep they reside in the
namespace tree. That makes is_ancestor overly complex (and therefore
bleeds over into unqualified namespace lookup)
This patch adds a SCOPE_DEPTH macro (it may be useful to extend to other
scope-like things). It uses th
The following patch ontop of early LTO debug patches get us back to
LTO bootstrap (see also the DW_OP_GNU_variable_value fixes / tweaks mail).
With early LTO debug we have to resolve DW_OP_GNU_variable_value early
as we are going to output the DIEs early. The following patch always
does that con
On Mon, May 15, 2017 at 3:19 PM, Jakub Jelinek wrote:
> 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
On 16/05/17 10:47 +0100, Jonathan Wakely wrote:
The bad names are not in a file called BADNAMES, so link from the old
chunk of documentation to the new position in the manual.
* doc/xml/manual/appendix_contributing.xml: Link to the list of bad
identifiers.
* doc/html/*: R
On 02/05/17 18:08, Martin Jambor wrote:
1. Add specs to drive the LLVM assembler and linker. It requires them to be
installed as "as" and "ld", under $target/bin, but then the compiler Just
Works with these specs.
...is that I do not have llvm linker at hand and without it I did not
manage to m
On 13 May 2017 at 11:38, Jakub Jelinek wrote:
> On Sat, May 13, 2017 at 12:24:12PM +0200, Bernhard Reutner-Fischer wrote:
>> I guess neither redhat
>> (https://access.redhat.com/downloads/content/dejagnu/ redirects to a
>> login page but there seem to be 1.5.1 packages) nor SuSE did update dejagnu
The bad names are not in a file called BADNAMES, so link from the old
chunk of documentation to the new position in the manual.
* doc/xml/manual/appendix_contributing.xml: Link to the list of bad
identifiers.
* doc/html/*: Regenerate.
Committed to trunk.
commit fe4721b0
Hi:
There are new failures between r248067 and r248036 on
mips64el-unknown-linux-gnu.
ERROR: gcc.target/mips/reorgbug-1.c -O0 : Unrecognised option: -O2
for " dg-options 1 "-O2 -msoft-float -mips2" "
UNRESOLVED: gcc.target/mips/reorgbug-1.c -O0 : Unrecognised
option: -O2 for " dg-options
Hello.
This fixes 2 typos in ipa-devirt.c, applying as obvious.
Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
Martin
>From 3ca7dbf8b4006813320852480509de1571cc3154 Mon Sep 17 00:00:00 2001
From: marxin
Date: Mon, 15 May 2017 15:44:27 +0200
Subject: [PATCH] Fix 2 typ
Hi Kyrill,
>
> Sorry for missing this.
> For the record you are referring to the patch at:
> https://gcc.gnu.org/ml/gcc-patches/2016-09/msg01700.html
>
> This is ok and in line with what we do for the f32 intrinsics.
> My only concern was that we can do this only if
> __ARM_FEATURE_FP16_VECTOR_AR
On 05/16/2017 07:00, Daniel Santos wrote:
>
> 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().
Here is what I am testing currently.
I fixed the
This patch just adds a helper function for getting the next strinfo
in a chain, since part 2 adds another place where we do that.
Tested on aarch64-linux-gnu and x86_64-linux-gnu. OK to install?
Thanks,
Richard
2017-05-16 Richard Sandiford
gcc/
* tree-ssa-strlen.c (get_next_strinfo
In this testcase, we (correctly) record after:
strcpy (p1, "abcde");
char *p2 = strchr (p1, '\0');
strcpy (p2, q);
that the length of p1 and p2 can be calculated by converting the
second strcpy to:
tmp = stpcpy (p2, q)
and then doing tmp - p1 for p1 and tmp - p2 for p2. This is delayed
Le 15/05/2017 à 23:58, Jeff Law a écrit :
> 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
>>
100 matches
Mail list logo
