Hi Shea,
Shea Levy skribis:
> Unlike the traditional approach of installing system libraries into one
> central location like /usr/{lib,include}, the nix package manager [1]
> installs each package into it's own prefix
> (e.g. /nix/store/mn9kqag3d24v6q41x747zd7n5qnalch7-zlib-1.2.8-dev).
Hi Ludo’,
Your patches look good! My biggest concern is how the ld wrapper behaves
in the presence of response files. Have you tested that?
Thanks,
Shea
Ludovic Courtès writes:
> Hi Shea,
>
> Shea Levy skribis:
>
>> Unlike the traditional approach of installing system libraries
Hi!
http://wg21.link/p0137
adds std::launder which is supposed to be some kind of aliasing optimization
barrier.
What is unclear to me is if we really need compiler support for that.
I have unfortunately not found many examples:
On Tue, Oct 18, 2016 at 1:06 PM, Jakub Jelinek wrote:
> Hi!
>
> http://wg21.link/p0137
> adds std::launder which is supposed to be some kind of aliasing optimization
> barrier.
>
> What is unclear to me is if we really need compiler support for that.
> I have unfortunately not
Hi!
Shea Levy skribis:
> Your patches look good! My biggest concern is how the ld wrapper behaves
> in the presence of response files. Have you tested that?
It surely doesn’t (yet?).
However, GCC does not pass “@file” arguments when it invokes ‘ld’, and
the bug report you
On Tue, Oct 18, 2016 at 8:59 AM, Ludovic Courtès via cfe-dev
wrote:
> Shea Levy skribis:
>
>> Your patches look good! My biggest concern is how the ld wrapper behaves
>> in the presence of response files. Have you tested that?
>
> It surely doesn’t
Hey Ludo’,
Amazing, more than a decade of close working with these tools and I
never knew about C_INCLUDE_PATH et al! It looks like those will solve a
huge portion of the problem.
Will look at your gcc and clang patches as well, thank you!
~Shea
Ludovic Courtès writes:
> Hi
Hi!
On Mon, 17 Oct 2016 15:38:50 +0200, I wrote:
> On Mon, 17 Oct 2016 14:08:44 +0200, Richard Biener
> wrote:
> > On Mon, Oct 17, 2016 at 1:47 PM, Thomas Schwinge
> > wrote:
> > > On Mon, 17 Oct 2016 13:22:17 +0200, Richard Biener
> > >
Snapshot gcc-5-20161018 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/5-20161018/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 5 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78033
--- Comment #2 from kargl at gcc dot gnu.org ---
(In reply to kargl from comment #1)
> Reduced testcase.
>
> function f(n, x)
>integer, intent(in) :: n
>complex, intent(in) :: x(1:n)
>real :: f
>f = g([real(x(1:n)),
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78033
kargl at gcc dot gnu.org changed:
What|Removed |Added
CC||kargl at gcc dot gnu.org
---
On 19 October 2016 at 03:03, Jeff Law wrote:
> On 10/17/2016 11:23 PM, Prathamesh Kulkarni wrote:
>>
>> The divmod transform isn't enabled if target supports hardware div in
>> the same or wider mode even if divmod libfunc is available for the
>> given mode.
>
> Good. That seems
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68649
--- Comment #18 from Joost VandeVondele
---
since this PR, and the related PR77278 can presumably only be fixed by changing
libgfortran abi (at least if I understand Richard's suggestion for fixing
this). The announced major version bump of
Hi Jonathan,
On 17 October 2016 at 13:56, Jonathan Wakely wrote:
> In C++17 the emplace_front and emplace_back members return a
> reference. There isn't a very neat way to implement this, so it's just
> lots of conditional compilation.
>
> This isn't an ABI break, because
On Thu, Oct 13, 2016 at 5:16 PM, Janne Blomqvist wrote:
> +static bool *newunits;
You could make this a bitmap (like sbitmap). A bit more code but makes
a potentially quadratic search (when opening many units) less time
consuming.
Ciao!
Steven
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78007
--- Comment #3 from Richard Biener ---
Created attachment 39827
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39827=edit
untested patch
Mostly untested prototype. For -mavx2 we get from the testcase innermost loop
.L6:
vmovdqa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78017
Bug ID: 78017
Summary: weak reference usage in gthr-posix.h (__gthread*) is
broken
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
On 10/17/2016 07:06 PM, Alexander Monakov wrote:
I've just pushed two commits to the branch to fix this issue. Before those, the
last commit left the branch in a state where an incremental build seemed ok
(because libgcc/libgomp weren't rebuilt with the new cc1), but a from-scratch
build was
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77943
--- Comment #13 from Martin Liška ---
The replacement you described fully makes sense for me! As I mentioned earlier,
I'm not c++ expert, I can't come up with more possible counter examples that
worth for testing.
However, we'll fix further
On Mon, Oct 17, 2016 at 6:57 PM, Senthil Kumar Selvaraj
wrote:
>
> Richard Biener writes:
>
>> On Mon, Oct 17, 2016 at 12:21 PM, Senthil Kumar Selvaraj
>> wrote:
>>> Hi,
>>>
>>> The fix for PR 52085 went into trunk when trunk
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78015
Jakub Jelinek changed:
What|Removed |Added
CC||rth at gcc dot gnu.org
--- Comment #1
On Tue, Oct 18, 2016 at 8:35 AM, Eric Botcazou wrote:
> Hi,
>
> this is a regression present on the mainline and 6 branch: the compiler now
> generates wrong code for the attached testcase at -O because of an internal
> conflict about boolean types. The sequence is as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78007
--- Comment #4 from Richard Biener ---
Probably handling should be moved after
targetm.vectorize.builtin_vectorized_function handling to allow arms
builtin-bswap vectorization via vrev to apply (not sure if its permutation
handling selects vrev
On Tue, Oct 18, 2016 at 12:17:32AM +0100, Iain Sandoe wrote:
> > Bootstrapped and tested on powerpc64-linux {-m64,-m32}. I'll commit it
> > if Iain's testing (on darwin) also succeeds.
>
> thanks!
>
> All-langs bootstrap was restored with the patch (and others in progress for
> existing known
Jakub Jelinek writes:
> On Tue, Oct 18, 2016 at 10:12:24AM +0200, Richard Biener wrote:
>> On Mon, Oct 17, 2016 at 6:57 PM, Senthil Kumar Selvaraj
>> wrote:
>> >
>> > Richard Biener writes:
>> >
>> >> On Mon, Oct 17, 2016 at 12:21 PM, Senthil Kumar Selvaraj
>>
On 10/17/2016 09:46 PM, tbsaunde+...@tbsaunde.org wrote:
+static inline void
+set_label_ref_label (rtx ref, rtx_insn *label)
+{
+ XCEXP (ref, 0, LABEL_REF) = label;
+}
I guess I have to ask for a brief function comment for this. Otherwise OK.
Bernd
> On Oct 17, 2016, at 7:21 PM, Pat Haugen wrote:
>
> On 10/17/2016 08:17 AM, Maxim Kuvyrkov wrote:
>>> The patch here, https://gcc.gnu.org/ml/gcc-patches/2014-10/msg01872.html,
>>> attempted to scale down the register limit used by -fsched-pressure for the
>>>
On 10/17/2016 09:46 PM, tbsaunde+...@tbsaunde.org wrote:
* cfgcleanup.c (merge_blocks_move_successor_nojumps): Adjust.
(outgoing_edges_match): Likewise.
(try_crossjump_to_edge): Likewise.
* cfgrtl.c (try_redirect_by_replacing_jump): Likewise.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78015
Bug ID: 78015
Summary: pthread_cancel while some exception is pending results
in std::terminate ()
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity:
On Mon, 17 Oct 2016, Andrew Pinski wrote:
> On Mon, Oct 17, 2016 at 5:26 AM, Richard Biener wrote:
> >
> > $subject, applied as obvious.
>
> I think you should do the same for the vectorizer too. I noticed that
> when testing the patch for loop splitting.
Can't see where
On Tue, Oct 18, 2016 at 10:12:24AM +0200, Richard Biener wrote:
> On Mon, Oct 17, 2016 at 6:57 PM, Senthil Kumar Selvaraj
> wrote:
> >
> > Richard Biener writes:
> >
> >> On Mon, Oct 17, 2016 at 12:21 PM, Senthil Kumar Selvaraj
> >>
On 18 October 2016 at 13:55, Richard Biener wrote:
> On Tue, 18 Oct 2016, Prathamesh Kulkarni wrote:
>
>> On 18 October 2016 at 02:46, Jeff Law wrote:
>> > On 10/15/2016 11:59 PM, Prathamesh Kulkarni wrote:
>> >>
>> >> This patch is mostly the same as previous
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78016
Bug ID: 78016
Summary: REG_NOTE order is not kept during insn copy
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66756
Dominique d'Humieres changed:
What|Removed |Added
Status|WAITING |NEW
--- Comment #5 from
On Tue, Oct 18, 2016 at 02:46:29PM +0530, Senthil Kumar Selvaraj wrote:
> > I'm not convinced it is desirable to backport such changes, it affects ABI,
> > people are used to deal with minor ABI changes in between major GCC
> > releases, but we'd need a strong reason to change it between minor
On 10/17/2016 09:46 PM, tbsaunde+...@tbsaunde.org wrote:
From: Trevor Saunders
gcc/ChangeLog:
2016-10-17 Trevor Saunders
* cfgrtl.c (delete_insn_chain): Change argument type to rtx_insn *
and adjust for that.
*
On 10/17/2016 09:46 PM, tbsaunde+...@tbsaunde.org wrote:
From: Trevor Saunders
gcc/ChangeLog:
2016-10-17 Trevor Saunders
* emit-rtl.c (prev_nonnote_insn_bb): Change argument type to
rtx_insn *.
* rtl.h
This fixes the BB_VISITED bug in IRA I ran into earlier this year,
removing the superfluous clearing in VRP and the SSA propagator as well
as removing the now always true do_dce flag from substitute-and-fold.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to trunk.
Richard.
Hi,
On 17 October 2016 at 18:47, Kyrill Tkachov wrote:
>
> On 30/09/16 14:34, Bernd Edlinger wrote:
>>
>> On 09/30/16 12:14, Bernd Edlinger wrote:
>>>
>>> Eric Botcazou wrote:
>
> A comment before the SETs and a testcase would be nice. IIRC
> we do have
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78015
--- Comment #2 from Jakub Jelinek ---
(In reply to Jakub Jelinek from comment #0)
> #ifdef WORKAROUND
> try
> {
> throw 1;
> }
> catch (int &)
> #endif
Oops, of course I meant #ifndef WORKAROUND. The problem is when there is an
Ping!
Regards
Senthil
Senthil Kumar Selvaraj writes:
> Bernd Schmidt writes:
>
>> On 09/16/2016 09:02 PM, Senthil Kumar Selvaraj wrote:
>>> Does this make sense? I ran a reg test for the avr target with a
>>> slightly older version of this patch, it did not show any regressions.
>>> If
The name of Etc/GMT+1 timezone is "-01", as evident from:
$ TZ=Etc/GMT+1 date +%Z
-01
Attached patch fixes the testsuite failure.
Uros.
diff --git a/libgo/go/time/time_test.go b/libgo/go/time/time_test.go
index b7ebb37..694e311 100644
--- a/libgo/go/time/time_test.go
+++
On 18 October 2016 at 05:18, Markus Trippelsdorf wrote:
> On 2016.10.18 at 05:13 +0200, Markus Trippelsdorf wrote:
>> On 2016.10.17 at 17:23 -0500, Bill Schmidt wrote:
>> > Hi,
>> >
>> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77916 identifies a situation
>> > where
[ sorry for losing track of this patch ]
On Sun, Oct 09, 2016 at 10:32:51AM +0200, Eric Botcazou wrote:
> > Use "mode" instead of "Pmode" here?
>
> No, "mode" is the mode of the MEM, not that of the SYMBOL_REF.
I still don't see it, could you explain a bit more?
Segher
> > No, "mode" is the mode of the MEM, not that of the SYMBOL_REF.
>
> I still don't see it, could you explain a bit more?
MODE is the mode of operands[1] before:
operands[1] = force_const_mem (mode, operands[1]);
and after. But the test is on the address of the MEM, not on the MEM
On 10/17/2016 09:46 PM, tbsaunde+...@tbsaunde.org wrote:
From: Trevor Saunders
gcc/ChangeLog:
2016-10-17 Trevor Saunders
* ccmp.c (expand_ccmp_expr_1): Adjust.
(expand_ccmp_expr): Likewise.
(expand_ccmp_next):
On Mon, 17 Oct 2016, Richard Biener wrote:
>
> This refactors propagation vs. substitution and handles condition
> simplification properly as well as passing a known taken edge down
> to the DOM walker (avoiding useless work and properly handling PHIs).
>
> If we do all the work it's stupid to
On Tue, 18 Oct 2016, Prathamesh Kulkarni wrote:
> On 18 October 2016 at 02:46, Jeff Law wrote:
> > On 10/15/2016 11:59 PM, Prathamesh Kulkarni wrote:
> >>
> >> This patch is mostly the same as previous one, except it drops
> >> targeting __udivmoddi4() because it gave undefined
> On Oct 18, 2016, at 1:27 PM, Maxim Kuvyrkov wrote:
>
>>
>> On Oct 17, 2016, at 7:21 PM, Pat Haugen wrote:
>>
>> On 10/17/2016 08:17 AM, Maxim Kuvyrkov wrote:
The patch here,
On 10/17/2016 09:46 PM, tbsaunde+...@tbsaunde.org wrote:
{
- rtx r0, r16, eqv, tga, tp, insn, dest, seq;
+ rtx r0, r16, eqv, tga, tp, dest, seq;
+ rtx_insn *insn;
switch (tls_symbolic_operand_type (x))
{
@@ -1025,66 +1026,70 @@ alpha_legitimize_address_1 (rtx
On Tue, Oct 18, 2016 at 10:12:24AM +0200, Richard Biener wrote:
> On Mon, Oct 17, 2016 at 6:57 PM, Senthil Kumar Selvaraj
> wrote:
> >
> > Richard Biener writes:
> >
> >> On Mon, Oct 17, 2016 at 12:21 PM, Senthil Kumar Selvaraj
> >>
On Mon, Oct 17, 2016 at 11:44 PM, Mike Stump wrote:
> On Oct 17, 2016, at 2:38 PM, Ximin Luo wrote:
>>
>> Mike Stump:
>>> On Oct 17, 2016, at 11:00 AM, Ximin Luo wrote:
Therefore, it is better to emit it in all circumstances,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78009
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78019
Bug ID: 78019
Summary: Local class with lambda in default member initializer
cannot default-capture this
Product: gcc
Version: 7.0
Status: UNCONFIRMED
On 2016.10.18 at 11:19 +0200, Christophe Lyon wrote:
> On 18 October 2016 at 05:18, Markus Trippelsdorf
> wrote:
> > On 2016.10.18 at 05:13 +0200, Markus Trippelsdorf wrote:
> >> On 2016.10.17 at 17:23 -0500, Bill Schmidt wrote:
> >> > Hi,
> >> >
> >> >
On Tue, Oct 18, 2016 at 12:09 PM, Steven Bosscher wrote:
> On Thu, Oct 13, 2016 at 5:16 PM, Janne Blomqvist wrote:
>> +static bool *newunits;
>
> You could make this a bitmap (like sbitmap). A bit more code but makes
> a potentially quadratic search (when opening many
On 10/17/2016 09:46 PM, tbsaunde+...@tbsaunde.org wrote:
2016-10-17 Trevor Saunders
* config/rl78/rl78.c (gen-and_emit_move): Change argument type
to rtx_insn *.
(transcode_memory_rtx): Likewise.
(move_to_acc): Likewise.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78018
Bug ID: 78018
Summary: [C++14] "internal compiler error: Segmentation fault"
with templates and lambdas
Product: gcc
Version: 6.2.0
Status: UNCONFIRMED
These variable templates give warnings in C++11 mode when
-Wsystem-headers is used:
In file included from /home/jwakely/gcc/7/include/c++/7.0.0/memory:77:0,
from vt.cc:1:
/home/jwakely/gcc/7/include/c++/7.0.0/bits/uses_allocator.h:130:20: warning:
variable templates only
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78019
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78018
Markus Trippelsdorf changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
Bernd Schmidt writes:
> On 10/13/2016 08:57 AM, Senthil Kumar Selvaraj wrote:
>>
>> 2016-10-13 Senthil Kumar Selvaraj
>>
>> * reload.c (find_valid_class_1): Allow regclass if atleast one
>> regno in class is ok. Compute and use rclass size based on
The following patch makes EVRP remove stmts that will become dead
after propagation. For this to work we have to propagate into PHIs
(sth we missed as well).
Bootstrap and regtest running on x86_64-unknown-linux-gnu.
Richard.
2016-10-18 Richard Biener
*
On Tue, Oct 18, 2016 at 02:34:58PM +0200, Richard Biener wrote:
>
> The following patch makes EVRP remove stmts that will become dead
> after propagation. For this to work we have to propagate into PHIs
> (sth we missed as well).
>
> Bootstrap and regtest running on x86_64-unknown-linux-gnu.
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77964
--- Comment #14 from Jiri Slaby ---
(In reply to Andrew Pinski from comment #10)
> (In reply to Markus Trippelsdorf from comment #9)
> > Is subtracting undefined, too?
> Yes. Comparing two unrelated arrays or subtracting them is undefined.
But
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77964
--- Comment #15 from Jakub Jelinek ---
(In reply to Jiri Slaby from comment #14)
> (In reply to Andrew Pinski from comment #10)
> > (In reply to Markus Trippelsdorf from comment #9)
> > > Is subtracting undefined, too?
> > Yes. Comparing two
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63907
--- Comment #10 from Klaus Rudolph ---
Created attachment 39830
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39830=edit
preprocessed file rwlock.ii
Add rwlock.ii file as requested.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78017
--- Comment #1 from Andrew Pinski ---
IIRC this was declared a libc bug or an user error (not using the full
archive). There is another thread on the glibc side if you want to read up on
that.
Hi,
When analyzing reg test failures for the avr target, I noticed that the
torture options were different when running dg-torture.exp compared to
x86_64-pc-linux-gnu, resulting in additional failures. I also found
that a bunch of "torture-without-loops not empty as expected" errors
On Tue, Oct 18, 2016 at 11:19 AM, Uros Bizjak wrote:
> The name of Etc/GMT+1 timezone is "-01", as evident from:
>
> $ TZ=Etc/GMT+1 date +%Z
> -01
>
> Attached patch fixes the testsuite failure.
Forgot to say that the patch was tested with tzdata2016g on Fedora 24
and CentOS
On Tue, 2016-10-18 at 05:13 +0200, Markus Trippelsdorf wrote:
> On 2016.10.17 at 17:23 -0500, Bill Schmidt wrote:
> > Hi,
> >
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77916 identifies a situation
> > where SLSR will ICE when exposed to a cast from integer to pointer. This
> > is because
On Tue, Oct 18, 2016 at 01:09:24PM +0200, Eric Botcazou wrote:
> > > No, "mode" is the mode of the MEM, not that of the SYMBOL_REF.
> >
> > I still don't see it, could you explain a bit more?
>
> MODE is the mode of operands[1] before:
>
> operands[1] = force_const_mem (mode,
On Tue, Oct 18, 2016 at 2:35 PM, Ximin Luo wrote:
> Richard Biener:
>> On Mon, Oct 17, 2016 at 11:44 PM, Mike Stump wrote:
>>> On Oct 17, 2016, at 2:38 PM, Ximin Luo wrote:
Mike Stump:
> On Oct 17, 2016, at 11:00 AM,
On Tue, Oct 18, 2016 at 2:10 PM, Uros Bizjak wrote:
> On Tue, Oct 18, 2016 at 11:19 AM, Uros Bizjak wrote:
>> The name of Etc/GMT+1 timezone is "-01", as evident from:
>>
>> $ TZ=Etc/GMT+1 date +%Z
>> -01
>>
>> Attached patch fixes the testsuite failure.
>
>
Hi Uros,
> On Tue, Oct 18, 2016 at 11:19 AM, Uros Bizjak wrote:
>> The name of Etc/GMT+1 timezone is "-01", as evident from:
>>
>> $ TZ=Etc/GMT+1 date +%Z
>> -01
>>
>> Attached patch fixes the testsuite failure.
>
> Forgot to say that the patch was tested with tzdata2016g on
While testing a libgo patch on Solaris, which does not support
split-stack, I ran across a bug in the handling of caller-saved
registers for the garbage collector. For non-split-stack systems,
runtime_mcall is responsible for saving all caller-saved registers on
the stack so that the GC stack
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63907
--- Comment #9 from Klaus Rudolph ---
hi all,
> Gesendet: Freitag, 14. Oktober 2016 um 10:32 Uhr
> Von: "redi at gcc dot gnu.org"
> An: lts-rudo...@gmx.de
> Betreff: [Bug libitm/63907] libitm/config/posix/rwlock.cc
Hi,
The previous solution for PR77916 was inadequately tested, for which I
sincerely apologize. I've reinstated the stopgap fix previously
reverted, as follows.
Thanks for your patience,
Bill
2016-10-18 Bill Schmidt
PR tree-optimization/77916
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77964
--- Comment #17 from Jakub Jelinek ---
(In reply to Jiri Slaby from comment #16)
> (In reply to Jakub Jelinek from comment #15)
> > lots of them that rely on pointer arithmetics being defined only within the
> > same object.
>
> Sure, but the
On 17/10/16 14:37 +0100, Jonathan Wakely wrote:
We are incorrectly requiring unique_ptr deleters to be copyable here:
explicit
unique_ptr(pointer __p) noexcept
: _M_t(__p, deleter_type())
{ }
We could just do:
explicit
unique_ptr(pointer __p) noexcept
: _M_t()
On 10/18/2016 02:15 PM, Senthil Kumar Selvaraj wrote:
Will do both the changes and re-run the reg tests. Ok for trunk if the
tests pass for x86_64-pc-linux and avr?
Probably but let's see the patch first.
Bernd
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77916
--- Comment #5 from Bill Schmidt ---
Author: wschmidt
Date: Tue Oct 18 13:35:19 2016
New Revision: 241305
URL: https://gcc.gnu.org/viewcvs?rev=241305=gcc=rev
Log:
2016-10-18 Bill Schmidt
PR
Richard Biener:
> On Mon, Oct 17, 2016 at 11:44 PM, Mike Stump wrote:
>> On Oct 17, 2016, at 2:38 PM, Ximin Luo wrote:
>>>
>>> Mike Stump:
On Oct 17, 2016, at 11:00 AM, Ximin Luo wrote:
> Therefore, it is better to emit it
On Tue, Oct 18, 2016 at 01:25:55PM +0200, Bernd Schmidt wrote:
> On 10/17/2016 09:46 PM, tbsaunde+...@tbsaunde.org wrote:
> > From: Trevor Saunders
> >
> > gcc/ChangeLog:
> >
> > 2016-10-17 Trevor Saunders
> >
> > * ccmp.c
On 2016.10.18 at 08:15 -0500, Bill Schmidt wrote:
> On Tue, 2016-10-18 at 05:13 +0200, Markus Trippelsdorf wrote:
> > On 2016.10.17 at 17:23 -0500, Bill Schmidt wrote:
> > > Hi,
> > >
> > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77916 identifies a situation
> > > where SLSR will ICE when
On Tue, 2016-10-18 at 15:30 +0200, Markus Trippelsdorf wrote:
> I you wish I can send you a tarball with the preprocessed *.i files from
> ffmpeg, so that you can use a stage1 cross on them.
>
That would be very helpful, thanks!
Bill
On Tue, 18 Oct 2016, Trevor Saunders wrote:
> On Tue, Oct 18, 2016 at 02:34:58PM +0200, Richard Biener wrote:
> >
> > The following patch makes EVRP remove stmts that will become dead
> > after propagation. For this to work we have to propagate into PHIs
> > (sth we missed as well).
> >
> >
For
extern void baz ();
extern void boo ();
extern void bla ();
int a[100];
void foo (int n)
{
for (int j = 0; j < n; ++j)
{
if (a[j+5])
{
if (a[j])
break;
baz ();
}
else
bla ();
boo ();
}
}
we happen to visit
On Tue, Oct 18, 2016 at 01:18:42PM +0200, Bernd Schmidt wrote:
> On 10/17/2016 09:46 PM, tbsaunde+...@tbsaunde.org wrote:
> > {
> > - rtx r0, r16, eqv, tga, tp, insn, dest, seq;
> > + rtx r0, r16, eqv, tga, tp, dest, seq;
> > + rtx_insn *insn;
> >
> >switch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77964
--- Comment #16 from Jiri Slaby ---
(In reply to Jakub Jelinek from comment #15)
> lots of them that rely on pointer arithmetics being defined only within the
> same object.
Sure, but the two pointers (taken implicitly of the arrays) are within
On 10/18/2016 03:54 PM, Trevor Saunders wrote:
I do really prefer reading code where variables are declared at first
use
In general, so do I, but in this case it's one variable out of a whole
bunch, which makes the entire thing look a little inconsistent.
Bernd
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65950
Andrew Pinski changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
hen compiled by gcc trunk dated 20161018,
and compiler flags -O3 -march=native, does this:
$ ../results/bin/gcc -c -O3 -march=native bug312.c
../../src/H5Tconv.c: In function ‘H5T__conv_int_float’:
../../src/H5Tconv.c:7558:1: internal compiler error: in replace_one_candidate,
at gimple-ssa-stren
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78023
--- Comment #3 from Uroš Bizjak ---
(In reply to David Binderman from comment #0)
> Created attachment 39831 [details]
> C source code after creduce
>
> The attached C code, when compiled by gcc trunk dated 20161018,
> and com
Hi,
in the language of our implementations details, submitter noticed that
in terms of warnings we handle in a different way COND_EXPRs in
tsubst_copy_and_build - we use fold_non_dependent_expr and integer_zerop
to suppress undesired warnings by bumping c_inhibit_evaluation_warnings
- and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78005
--- Comment #4 from amker at gcc dot gnu.org ---
Hmm, some code got lost during iterating of patch testing... Will send a patch
soon.
On Mon, Oct 17, 2016 at 12:40:18PM +, Wilco Dijkstra wrote:
>
> ping
>
> If the number of integer callee-saves is odd, the FP callee-saves use 8-byte
> aligned LDP/STP. Since 16-byte alignment may be faster on some CPUs, align
> the FP callee-saves to 16 bytes and use the alignment gap for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41861
--- Comment #14 from Mike Crowe ---
(In reply to Jonathan Wakely from comment #13)
> (In reply to Roman Fietze from comment #12)
> > Sorry if it is inappropriate to ask for any changes, but how can it be, that
> > there is no fix for this bug
Hello!
> This patch copies the code that implements the print and println
> predeclared functions from the Go 1.7 runtime. The compiler is
> changed to use the new names, and to call the printlock and
> printunlock functions around a sequence of print calls. The writebuf
> field in the g struct
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78016
Eric Botcazou changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
1 - 100 of 209 matches
Mail list logo