Ping
From: Tamar Christina
Sent: Monday, July 3, 2017 7:12:05 AM
To: James Greenhalgh
Cc: GCC Patches; nd; Marcus Shawcroft; Richard Earnshaw
Subject: Re: [PATCH][GCC][AArch64] optimize float immediate moves (2 /4) -
HF/DF/SF mode.
Ping
___
Ping
From: Tamar Christina
Sent: Monday, July 3, 2017 7:11:51 AM
To: James Greenhalgh
Cc: Richard Sandiford; GCC Patches; nd; Marcus Shawcroft; Richard Earnshaw
Subject: Re: [PATCH][GCC][AArch64] optimize float immediate moves (1 /4) -
infrastructure.
Ping
Hi Andreas,
On 08/07/17 21:48, Andreas Schwab wrote:
This breaks gcc.dg/asan/pr80168.c on aarch64 -mabi=ilp32:
/opt/gcc/gcc-20170708/gcc/testsuite/gcc.dg/asan/pr80168.c:7:1: internal
compiler error: in emit_library_call_value_1, at calls.c:4555
0x701577 emit_library_call_value_1
../..
On Fri, Jul 07, 2017 at 11:01:51AM -0600, Jeff Law wrote:
> On 07/06/2017 07:25 AM, Daniel P. Berrange wrote:
> > There are several hundred named attribute keys that have been
> > introduced over many GCC releases. Applications typically need
> > to be compilable with multiple GCC versions, so it i
Hi,
On 6 July 2017 at 06:50, Jeff Law wrote:
> On 07/04/2017 02:50 AM, Christophe Lyon wrote:
>> On 3 July 2017 at 17:30, Jeff Law wrote:
>>> On 07/03/2017 09:00 AM, Christophe Lyon wrote:
Hi,
This is a follow-up to
https://gcc.gnu.org/ml/gcc-patches/2017-06/msg01791.html
>>
On Tue, Jul 4, 2017 at 1:29 PM, Richard Biener
wrote:
> On Tue, Jul 4, 2017 at 2:06 PM, Bin.Cheng wrote:
>> On Tue, Jul 4, 2017 at 12:19 PM, Richard Biener
>> wrote:
>>> On Mon, Jul 3, 2017 at 4:17 PM, Bin.Cheng wrote:
On Mon, Jul 3, 2017 at 10:38 AM, Richard Biener
wrote:
> On T
On Tue, Jun 27, 2017 at 11:49 AM, Bin Cheng wrote:
> Hi,
> This is a followup patch better handling below case:
> for (i = 0; i < n; i++)
>{
> a[i] = 1;
> a[i+2] = 2;
>}
> Instead of generating root variables by loading from memory and propagating
> with PHI
On 07/07/2017 09:20 PM, Martin Sebor wrote:
> A conflict in my patch for bug 81345 made me notice that r249734
> recently added a new option property, IntegerRange. The change
> below adds brief documentation of the property to the manual.
>
> Martin, can you please check to make sure I didn't mi
On Jun 27 2017, Joseph Myers wrote:
> Testing compilation together with current glibc with glibc's
> build-many-glibcs.py. OK to commit (mainline and active release
> branches) if that passes?
This still doesn't work on the gcc-6-branch:
In file included from ../../../libjava/prims.cc:26:0:
..
On 2017-07-07 18:04, Eric Botcazou wrote:
Great! Would you mind to apply the patch for us? The only person here
with write access just went on vacation. I have submitted a new version
(v4) with the change that applies to both main and 7.
OK, will do.
Thanks!
--
Daniel Cederman
Cobham Gais
Hi Bin,
On 30 June 2017 at 12:43, Bin.Cheng wrote:
> On Wed, Jun 28, 2017 at 2:09 PM, Bin.Cheng wrote:
>> On Wed, Jun 28, 2017 at 1:29 PM, Richard Biener
>> wrote:
>>> On Wed, Jun 28, 2017 at 1:46 PM, Bin.Cheng wrote:
On Wed, Jun 28, 2017 at 11:58 AM, Richard Biener
wrote:
> On
Hi Yuri,
On 09/07/17 20:06, Yuri Gribov wrote:
Hi,
Currently dg-cmp-results fails to compare fails in Asan tests because
their output includes failing process id:
NA->FAIL: c-c++-common/asan/bitfield-1.c -O0 output pattern test,
is ==18161==ERROR
FAIL->NA: c-c++-common/asan/bitfield-1.c -O
Hello
Following patch disables -fgnu-tm with AddressSanitizer.
Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
Ready to be installed?
Martin
gcc/ChangeLog:
2017-07-04 Martin Liska
PR sanitizer/81302
* opts.c (finish_options): Do not allow -fgnu-tm
Hi.
This adds missing quotes to various error messages related to AddressSanitizer.
Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
Ready to be installed?
Martin
gcc/ChangeLog:
2017-07-04 Martin Liska
* opts.c (finish_options): Add quotes to error message
On Mon, Jul 10, 2017 at 10:32 AM, Christophe Lyon
wrote:
> Hi Bin,
>
> On 30 June 2017 at 12:43, Bin.Cheng wrote:
>> On Wed, Jun 28, 2017 at 2:09 PM, Bin.Cheng wrote:
>>> On Wed, Jun 28, 2017 at 1:29 PM, Richard Biener
>>> wrote:
On Wed, Jun 28, 2017 at 1:46 PM, Bin.Cheng wrote:
> On
On Mon, Jul 10, 2017 at 10:32 AM, Thomas Preudhomme
wrote:
> Hi Yuri,
>
> On 09/07/17 20:06, Yuri Gribov wrote:
>>
>> Hi,
>>
>> Currently dg-cmp-results fails to compare fails in Asan tests because
>> their output includes failing process id:
>> NA->FAIL: c-c++-common/asan/bitfield-1.c -O0 outp
Hi all,
I've rebased the previous patch to trunk per Andrew's suggestion.
Original patch description/motivation/questions are in
https://gcc.gnu.org/ml/gcc-patches/2017-06/msg01869.html
-Y
safe-unwind-2.patch
Description: Binary data
#include
#include
struct _Unwind_Context;
typedef int (*_
Hi all,
This is a new version of previous patch
(https://gcc.gnu.org/ml/gcc-patches/2017-07/msg00020.html), fixed
after Rainer's remarks.
-Y
pr56727-2.patch
Description: Binary data
On 08.07.2017 06:58, Denis Chertykov wrote:
2017-07-07 18:31 GMT+04:00 Georg-Johann Lay :
Hi,
this patch addresses a very old issue, the non-optimal
generation of ISR prologues and epilogues.
As GAS now provides the __gcc_isr pseudo instruction to
overcome some problems, see
https://sourcewar
On Sat, 8 Jul 2017, Yuri Gribov wrote:
> On Fri, Jul 7, 2017 at 11:51 PM, Joseph Myers wrote:
> > On Fri, 7 Jul 2017, Yuri Gribov wrote:
> >
> >> > I suspect infinities would already work with the patch as-is (the logic
> >> > dealing with constants outside the range of the integer type). I'm le
On Mon, Jul 10, 2017 at 11:06 AM, Joseph Myers wrote:
> On Sat, 8 Jul 2017, Yuri Gribov wrote:
>
>> On Fri, Jul 7, 2017 at 11:51 PM, Joseph Myers
>> wrote:
>> > On Fri, 7 Jul 2017, Yuri Gribov wrote:
>> >
>> >> > I suspect infinities would already work with the patch as-is (the logic
>> >> > dea
On Mon, 10 Jul 2017, Andreas Schwab wrote:
> On Jun 27 2017, Joseph Myers wrote:
>
> > Testing compilation together with current glibc with glibc's
> > build-many-glibcs.py. OK to commit (mainline and active release
> > branches) if that passes?
>
> This still doesn't work on the gcc-6-branch:
On Jul 10 2017, Joseph Myers wrote:
> On Mon, 10 Jul 2017, Andreas Schwab wrote:
>
>> On Jun 27 2017, Joseph Myers wrote:
>>
>> > Testing compilation together with current glibc with glibc's
>> > build-many-glibcs.py. OK to commit (mainline and active release
>> > branches) if that passes?
>>
On Mon, 10 Jul 2017, Yuri Gribov wrote:
> On Mon, Jul 10, 2017 at 11:06 AM, Joseph Myers
> wrote:
> > On Sat, 8 Jul 2017, Yuri Gribov wrote:
> >
> >> On Fri, Jul 7, 2017 at 11:51 PM, Joseph Myers
> >> wrote:
> >> > On Fri, 7 Jul 2017, Yuri Gribov wrote:
> >> >
> >> >> > I suspect infinities wo
Hi
I write some codes to make gcc support comparison-guided fuzzing.
It is very like
http://clang.llvm.org/docs/SanitizerCoverage.html#tracing-data-flow .
With -fsanitize-coverage=trace-cmp the compiler will insert extra
instrumentation around comparison instructions and switch statements.
I thi
On Mon, Jul 03, 2017 at 01:32:46PM -0400, David Malcolm wrote:
> On Mon, 2017-07-03 at 10:25 -0600, Jeff Law wrote:
> > On 05/05/2017 11:51 AM, David Malcolm wrote:
> > > In various places we use lookup_name_fuzzy to provide a hint,
> > > and can report messages of the form:
> > > error: unknown
[adding Mike Stump who approved my last patch to dg-cmp-results]
Hi Yuri,
On 09/07/17 20:06, Yuri Gribov wrote:
Hi,
Currently dg-cmp-results fails to compare fails in Asan tests because
their output includes failing process id:
NA->FAIL: c-c++-common/asan/bitfield-1.c -O0 output pattern tes
On 06/07/17 20:23 +0300, Ivan Baravy wrote:
On 07/05/2017 10:00 PM, Jonathan Wakely wrote:
This patch adds AddressSanitizer annotations to std::vector, so that
ASan can detect out-of-bounds accesses to the unused capacity of a
vector. e.g.
std::vector v(2);
int* p = v.data();
v.pop_back()
On Mon, Jul 10, 2017 at 1:13 PM, Thomas Preudhomme
wrote:
> [adding Mike Stump who approved my last patch to dg-cmp-results]
>
> Hi Yuri,
>
> On 09/07/17 20:06, Yuri Gribov wrote:
>>
>> Hi,
>>
>> Currently dg-cmp-results fails to compare fails in Asan tests because
>> their output includes failing
Approved and applied.
Cheers,
Claudiu
> -Original Message-
> From: Vineet Gupta
> Sent: Friday, May 20, 2016 7:02 AM
> To: gcc-patches@gcc.gnu.org
> Cc: Claudiu Zissulescu ; g...@amylaar.uk;
> francois.bed...@synopsys.com; Vineet Gupta
> Subject: [PATCH] ARC: configure script to allow no
> > gcc/testsuite
> > 2017-01-09 Claudiu Zissulescu
> >
> > * gcc.target/arc/mulsi3_highpart-1.c: Remove 'X' constraint.
> > * gcc.target/arc/mulsi3_highpart-2.c: Likewise.
>
> This looks fine and could be applied straight away I think.
>
> Thanks,
> Andrew
>
Committed. Thank you for
> > gcc/
> > 2017-01-09 Claudiu Zissulescu
> >
> > * config/arc/arc.h (ADDITIONAL_REGISTER_NAMES): Define.
>
> This looks fine and could be applied straight away I think.
>
> Thanks,
> Andrew
Committed. Thank you for your review,
Claudiu
Hi,team:
The following doc for memory_constraint and special_memory_constraint seems
imply that the handling of the special_memory_constraint in lra-constraints.c
is NOT correct:
(https://gcc.gnu.org/onlinedocs/gccint/Define-Constraints.html#Define-Constraints)
MD Expression: define_memory_cons
Hi,
The new instructions in FPV5-SP-D16 compared to FPv4-SP-D16 are not
generated when building libgcc, newlib of libstdc++ such that libgcc.a,
libc.a and libstdc++.a have the same objdump output for these two
variants. It is therefore a waste of build time to be building a
multilib for ARMv7E-M
Hi,
This patch fixes an ICE in new loop distribution code. When computing
topological
order for basic blocks it should record the max index of basic block, rather
than
number of basic blocks. I didn't add new test because existing tests can catch
the
ICE as well.
Bootstrap and test on x86_64.
Hi,
gently pinging this. As you can see certainly isn't an high priority
issue but resolving it one way or the other seems pretty simple...
On 16/06/2017 15:47, Paolo Carlini wrote:
Hi,
submitter and Manuel analyzed this a while ago and came to the
conclusion - which I think is still valid
On Fri, Jul 07, 2017 at 07:14:25PM -0500, Peter Bergner wrote:
> On 7/7/17 4:13 PM, Peter Bergner wrote:
> > On 7/7/17 10:18 AM, Segher Boessenkool wrote:
> >> On Thu, Jul 06, 2017 at 04:21:48PM -0500, Peter Bergner wrote:
> >>> * config/rs6000/float128-ifunc.c: Don't include auxv.h.
> >>> (hav
Likewise for embedded-7-branch.
Best regards,
Thomas
On 10/07/17 15:16, Thomas Preudhomme wrote:
Hi,
The new instructions in FPV5-SP-D16 compared to FPv4-SP-D16 are not
generated when building libgcc, newlib of libstdc++ such that libgcc.a,
libc.a and libstdc++.a have the same objdump output
On 07/10/2017 02:35 AM, Martin Liška wrote:
On 07/07/2017 09:20 PM, Martin Sebor wrote:
A conflict in my patch for bug 81345 made me notice that r249734
recently added a new option property, IntegerRange. The change
below adds brief documentation of the property to the manual.
Martin, can you
Hi All,
I've re-spun the patch with the changes requested.
This is only done when not honoring signaling NaNs.
This transormation is done at expand time by using
a new optab "xorsign". If the optab is not available
then copysign is expanded as normal.
Bootstrapped on both aarch64-none-linux-gnu
Hi All,
As the mid-end patch has been respun I've had to respin this one as well.
So this is a new version and a ping as well.
The patch provides AArch64 optabs for XORSIGN, both vectorized and scalar.
This patch is a revival of a previous patch
https://gcc.gnu.org/ml/gcc-patches/2015-10/msg000
Ping #2 of Volker's patch:
https://gcc.gnu.org/ml/gcc-patches/2017-04/msg01576.html
The patch reverts the format used in the output of enumerated
types from the 'E {enum}' notation introduced in r247347 to just
'E' or to the standard 'enum E' with %#qT.
Nathan, unless you have concerns with or
GCC Maintainers:
The following patch adds support for the vec_parity builtin. The
patch has been tested on powerpc64le-unknown-linux-gnu (Power 8 LE). On
this platform the test results in 1 unsupported tests, as expected. The
patch was tested on powerpc64-unknown-linux-gnu(Power 9 LE). The resu
On Thu, Jun 01, 2017 at 11:54:33PM +, Michael Collison wrote:
> This patch improves code generation for relational compares against zero that
> are not merged into a subtract instruction. This patch improves the >= and <
> cases.
>
> An example of the '<' case:
>
> int lt (int x, int y)
> {
>
Hi Carl,
On Mon, Jul 10, 2017 at 10:06:54AM -0700, Carl Love wrote:
> --- /dev/null
> +++ b/gcc/testsuite/gcc.target/powerpc/builtins-2-p9-runnable.c
> @@ -0,0 +1,72 @@
> +/* { dg-do run { target { powerpc64*-*-* && { lp64 && p9vector_hw } } } } */
powerpc*-*-* instead?
The patch looks fine to m
This fixes two problems with basic_stringbuf when using SSO strings.
Firstly, overflow() won't try to use excess capacity in the string
(which is present on construction, due to the SSO buffer, which can't
be utilised immediately due to LWG 2995, see PR 80676). That causes
overflow to allocate a
This allows using non-DefaultConstructible and stateful allocators
with basic_stringbuf, by copying the allocator from the basic_string.
PR libstdc++/81381
* include/bits/sstream.tcc (basic_stringbuf::overflow)
(basic_stringbuf::basic_stringbuf(const __string_type&, ios::m
On Jul 9, 2017, at 12:06 PM, Yuri Gribov wrote:
>
> Currently dg-cmp-results fails to compare fails in Asan tests because
> their output includes failing process id:
> NA->FAIL: c-c++-common/asan/bitfield-1.c -O0 output pattern test,
> is ==18161==ERROR
> FAIL->NA: c-c++-common/asan/bitfield-1
The memory leak cleanup has introduced a testsuite failure on AIX:
/nasfarm/edelsohn/src/src/libstdc++-v3/testsuite/abi/pr42230.cc: In
function 'int main()':
/nasfarm/edelsohn/src/src/libstdc++-v3/testsuite/abi/pr42230.cc:15:
error: 'free' is not a member of 'std'
compiler exited with status 1
On 10/07/17 14:32 -0400, David Edelsohn wrote:
The memory leak cleanup has introduced a testsuite failure on AIX:
/nasfarm/edelsohn/src/src/libstdc++-v3/testsuite/abi/pr42230.cc: In
function 'int main()':
/nasfarm/edelsohn/src/src/libstdc++-v3/testsuite/abi/pr42230.cc:15:
error: 'free' is not a
Hello world,
with the bump in the libfortran version that is needed with
Paul's patch, I think we can get rid of a few functions
that we do not actually need any more.
I think we now always inline SUM and PRODUCT. We don't do so with all
occurrences of ANY and ALL, but we probably could (and sho
On 07/10/2017 03:36 AM, Martin Liška wrote:
Hi.
This adds missing quotes to various error messages related to AddressSanitizer.
Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
Ready to be installed?
Martin
gcc/ChangeLog:
2017-07-04 Martin Liska
* opts.c
On 7/10/17 9:48 AM, Segher Boessenkool wrote:
> On Fri, Jul 07, 2017 at 07:14:25PM -0500, Peter Bergner wrote:
>> On 7/7/17 4:13 PM, Peter Bergner wrote:
>>> On 7/7/17 10:18 AM, Segher Boessenkool wrote:
On Thu, Jul 06, 2017 at 04:21:48PM -0500, Peter Bergner wrote:
> * config/rs6000/flo
On 07/07/2017 10:58 AM, Joseph Myers wrote:
This patch is OK.
Thanks. Committed in r250104.
Do you have any comments on or concerns with changing how
LangEnabledBy interprets the opt argument as I suggested below?
IMO, it makes little sense for an option that takes an argument
and that
Ping:
https://gcc.gnu.org/ml/gcc-patches/2017-07/msg00036.html
On 07/02/2017 02:00 PM, Martin Sebor wrote:
The attached patch enhances the -Wrestrict warning to detect more
than just trivial instances of overlapping copying by sprintf and
related functions.
The meat of the patch is relativel
On Jul 10, 2017, at 2:44 AM, Yuri Gribov wrote:
>
> On Mon, Jul 10, 2017 at 10:32 AM, Thomas Preudhomme
> wrote:
>> Hi Yuri,
>>
>> On 09/07/17 20:06, Yuri Gribov wrote:
>>>
>>> Hi,
>>>
>>> Currently dg-cmp-results fails to compare fails in Asan tests because
>>> their output includes failing
Hello,
Le 10/07/2017 à 20:43, Thomas Koenig a écrit :
Hello world,
with the bump in the libfortran version that is needed with
Paul's patch, I think we can get rid of a few functions
that we do not actually need any more.
I think we now always inline SUM and PRODUCT. We don't do so with all
oc
On Mon, Jul 10, 2017 at 8:43 PM, Thomas Koenig wrote:
> with the bump in the libfortran version that is needed with
> Paul's patch,
Isn't it time to start thinking about ABI compatibility just as for
the other libraries?
On Jul 10, 2017, at 2:21 PM, Mike Stump wrote:
>
> Someone with such a system will have to drill down into why.
Found it, fixed in dejagnu 1.5.3, just use a newer dejagnu, 1.5.3 or later
should be fine.
Apparently, I should have just checked it _first_. I didn't expect the fix to
lie there.
On Jul 9, 2017, at 12:00 PM, Yuri Gribov wrote:
>
> This patch fixes AutoFDO Dejagnu tests to print relative filenames
> instead of absolute ones when AutoFDO is unsupported. This is to
> prevent spurious differences in dg-cmp-results.sh, like this:
> NA->UNSUPPORTED:
> /home/yugr/src/gcc-57371/
Hello!
We have to use TARGET_SSE with TARGET_SSE_MATH in insn constraints.
2017-07-10 Uros Bizjak
PR target/81375
* config/i386/i386.md (divsf3): Add TARGET_SSE to TARGET_SSE_MATH.
(rcpps): Ditto.
(*rsqrtsf2_sse): Ditto.
(rsqrtsf2): Ditto.
(div3): Macroize insn from di
Am 10.07.2017 um 23:27 schrieb Mikael Morin:
We don’t inline when the dim argument isn’t constant. As far as I know,
this is a valid albeit rare use case for the library functions.
You're right. We can only remove, for example, sum_i4, but have
to keep ssum_i4 and msum_i4, which both take a d
On Mon, 10 Jul 2017, Martin Sebor wrote:
> On 07/07/2017 10:58 AM, Joseph Myers wrote:
> > This patch is OK.
> >
>
> Thanks. Committed in r250104.
>
> Do you have any comments on or concerns with changing how
> LangEnabledBy interprets the opt argument as I suggested below?
>
> IMO, it make
Dear All,
We are not quite there yet. Thanks to the posters to the thread on
clf, I have now been convinced that ptr => der_type_array%comp must
return an lbound=1 based descriptor, since the target is not a WHOLE
ARRAY as defined in the standard. In addition, Dominique picked up a
failing testcas
On Mon, Jul 10, 2017 at 10:52 PM, Mike Stump wrote:
> On Jul 10, 2017, at 2:21 PM, Mike Stump wrote:
>>
>> Someone with such a system will have to drill down into why.
>
> Found it, fixed in dejagnu 1.5.3, just use a newer dejagnu, 1.5.3 or later
> should be fine.
>
> Apparently, I should have j
65 matches
Mail list logo
