On Tue, Feb 19, 2019 at 11:03:05PM +0100, Jakub Jelinek wrote:
> > Before P0137 I believe foo and bar were arguably undefined.
>
> I see, before that it was:
> "an lvalue-to-rvalue conversion (4.1) or modification (5.18, 5.2.6, 5.3.2)
> that is applied
> to a glvalue that refers to a non-active m
Hi!
On Tue, Feb 19, 2019 at 05:31:28AM +0100, Jakub Jelinek wrote:
> > > + /* These builtins will fold into
> > > +(cast)
> > > + ((something = __real__ SAVE_EXPR <.???_OVERFLOW (cst1, cst2)>),
> > > + __imag__ SAVE_EXPR <.???_OVERFLOW (cst1, cst2)>)
> > > +which fails is_consta
On Tue, Feb 19, 2019 at 9:14 PM H.J. Lu wrote:
>
> On Tue, Feb 19, 2019 at 6:16 AM Uros Bizjak wrote:
> >
> > On Tue, Feb 19, 2019 at 2:49 PM H.J. Lu wrote:
> > >
> > > ix86_fpmath should be set to combination of FPMATH_387 and FPMATH_SSE.
> > > When SSE is disabled, it should be set to FPMATH_3
On 19 February 2019 19:18:21 CET, Steve Kargl
wrote:
>On Mon, Feb 18, 2019 at 02:23:34PM +0100, Martin Liška wrote:
>>
>> As I installed all needed patches, I'm sending a documentation entry
>> for the new functionality.
>>
>> Thoughts?
>
>See below. Ok to commit with suggested changes.
>
>> T
Yes, you are correct. If there is no question with this patch,
I will backport this to GCC 8.
Thanks,
Lijia
On 2019/2/20 12:13 PM, Bill Schmidt wrote:
On 2/19/19 8:11 AM, Segher Boessenkool wrote:
Hi!
On Tue, Feb 19, 2019 at 03:38:56AM -0600, Li Jia He wrote:
GCC revision 259524 implemented
On 2/19/19 8:11 AM, Segher Boessenkool wrote:
> Hi!
>
> On Tue, Feb 19, 2019 at 03:38:56AM -0600, Li Jia He wrote:
>> GCC revision 259524 implemented range check for the vec_splat_{su}{8,16,32}
>> builtins. However, as a consequence of the implementation, the range check
>> is not done correctly f
Since my patch for 81359 allowed us to signal failure on return from
maybe_instantiate_noexcept, we no longer need to turn an error into
noexcept(false). We also need to handle NSDMI instantiation errors under
synthesized_method_walk. This change caused some instantiation context
notes to be lost
A type in an anonymous namespace can never be merged with one from
another translation unit, so a member of such a type is always its own
prevailing decl.
I don't really understand the LTO concept of prevailing decl, or why we don't
get here if the destructor is defined, but this seems reasonable
Hi Segher,
On 2019/2/20 AM6:24, Segher Boessenkool wrote:
Hi!
On Tue, Feb 19, 2019 at 01:23:53AM -0600, luo...@linux.ibm.com wrote:
This is a backport of r25, r257253 and r258137 of trunk to gcc-7-branch.
The patches were on trunk before GCC 8 forked already. Totally 5 files need
mannual r
On 2/19/19 10:18 AM, Joseph Myers wrote:
On Tue, 19 Feb 2019, Martin Sebor wrote:
Sure, the text is in a section named Program startup, but that doesn't
imply that the constraints apply only at program startup. If they did,
I think it's clear from the context that the section is describing t
I received feedback on the first patch that it doesn't suppress all
the instances of the warning so I've relaxed the checker even more
to avoid the excess instances seen in Elfutils and beefed up
the tests. The top of trunk compiles cleanly now with just
the three instances of -Wformat-truncation
On 2/18/19 11:52 AM, Martin Sebor wrote:
Index: gcc/doc/extend.texi
===
--- gcc/doc/extend.texi (revision 268992)
+++ gcc/doc/extend.texi (working copy)
@@ -12890,6 +12890,23 @@ built-in in this case, because it has no opportuni
opt
One of the testsuite tests for libvtv is failing due to an incorrect
signature for the function
"main". This patch fixes that.
Testing: The libvtv testsuite failed 4 tests without this fix; it
passes all of them with it.
Ok to commit?
-- Caroline Tice
cmt...@google.com
Index: libvtv/ChangeLog
Bob,
Some of us still use varargs interfaces (in my case, Fortran calling C
stdarg subroutines).
The problem for us is that that sometimes using varargs made standard-
conforming Fortran code like, in file a.f
subroutine foo(a)
print *,a
end
and in file main.f
progra
Here is a patch to use the new TARGET_GET_MULTILIB_ABI_NAME macro that
Martin Liska added with the Aarch64 platform. The main issue to
consider is what abi names to support, I created 8 versions for big-
endian/little-endian, ilp32/lp64, and sve/non-sve. I am not sure if we
need all of those but
Hi!
On Tue, Feb 19, 2019 at 01:23:53AM -0600, luo...@linux.ibm.com wrote:
> This is a backport of r25, r257253 and r258137 of trunk to gcc-7-branch.
> The patches were on trunk before GCC 8 forked already. Totally 5 files need
> mannual resolve due to code changes for r25. r257253 and r258
On Tue, Feb 19, 2019 at 11:28:22AM -1000, Jason Merrill wrote:
> On Tue, Feb 19, 2019 at 4:00 AM Jakub Jelinek wrote:
> > On Mon, Feb 18, 2019 at 03:01:14PM -1000, Jason Merrill wrote:
> > > But it's not clear to me that the standard actually allows this. I don't
> > > think changing the active m
Hello world,
the attached patch fixes the 8/9 regression by inserting the conversion
at the right place. Regression-tested. OK for trunk, and for 8 when it
re-opens?
Regards
Thomas
2019-02-19 Thomas Koenig
PR fortran/86110
* class.c (gfc_get_len_component): Add arg
OK.
On Tue, Feb 19, 2019 at 1:16 AM Paolo Carlini wrote:
>
> Hi,
>
> On 19/02/19 02:39, Jason Merrill wrote:
> > On 2/18/19 3:15 PM, Paolo Carlini wrote:
> >> Hi,
> >>
> >> On 19/02/19 00:52, Jason Merrill wrote:
> >>> On 2/18/19 12:14 PM, Paolo Carlini wrote:
> Hi Jason,
>
> On 18
On Tue, Feb 19, 2019 at 4:00 AM Jakub Jelinek wrote:
> On Mon, Feb 18, 2019 at 03:01:14PM -1000, Jason Merrill wrote:
> > But it's not clear to me that the standard actually allows this. I don't
> > think changing the active member of a union in the mem-initializer for
> > another member is reaso
Power9 added support for V16QImode SAD operations. While making the
check_effective_target change I noticed that the tests will also pass on
Power7/Power8 even though they don't have the optab support. The reason is the
tests are only checking that the source pattern is recognized, not that a
S
Test FAILS: sse2-cvtpd2dq-1, sse2-cvtpd2ps, sse2-cvttpd2dq on powerpc64
(big-endian).
_mm_cvtpd_epi32, _mm_cvtpd_ps, _mm_cvttpd_epi32: Type conversion from
vector doubleword type to vector word type leaves the results in even
lanes in big endian mode.
Test FAILS: sse-cvtss2si-1, sse-cvtss2si-2, s
On Tue, Feb 19, 2019 at 6:16 AM Uros Bizjak wrote:
>
> On Tue, Feb 19, 2019 at 2:49 PM H.J. Lu wrote:
> >
> > ix86_fpmath should be set to combination of FPMATH_387 and FPMATH_SSE.
> > When SSE is disabled, it should be set to FPMATH_387 and 387 codegen is
> > also controlled by -msoft-float.
> >
On Thu, Feb 14, 2019 at 05:30:52PM +0100, Eric Botcazou wrote:
> > Yeah, something like that. It will need some serious testing, to make
> > sure we don't regress (including not regressing what that patch that took
> > them away was meant to do). I can arrange some testing, will you do the
> > pa
On Tue, Feb 19, 2019 at 02:44:55PM -0500, David Malcolm wrote:
> How about something like this? (on top of Jakub's patch)
I had following queued for regtest, so if you want to go for the
make_location ^~, you should change more spots.
> pr89390.C: In function 'void foo()':
> pr89390.C:9:6: error:
On Tue, Feb 12, 2019 at 02:00:38PM +0800, Xiong Hu Luo wrote:
> On 2019/1/26 AM1:43, Segher Boessenkool wrote:
> >On Wed, Jan 23, 2019 at 03:57:28AM -0600, luo...@linux.vnet.ibm.com wrote:
> >>The 5 new builtins vec_sbox_be, vec_cipher_be, vec_cipherlast_be,
> >>vec_ncipher_be
> >>and vec_ncipherl
On Mon, 2019-02-18 at 14:07 -1000, Jason Merrill wrote:
> On 2/18/19 12:50 PM, Jakub Jelinek wrote:
> > Hi!
> >
> > On the following testcase we ICE because name is BIT_NOT_EXPR and
> > suggest_alternative_in_scoped_enum assumes it is called on
> > IDENTIFIER_NODE
> > only.
> >
> > Fixed thusly,
Fix pr88850.c testcase which was failing in hardfp environments.
Committed as obvious.
ChangeLog:
2019-02-19 Wilco Dijkstra
* gcc.target/arm/pr88850.c: Block -mfloat-abi override.
--
diff --git a/gcc/testsuite/gcc.target/arm/pr88850.c
b/gcc/testsuite/gcc.target/arm/pr88850.c
index
This patch to the Go frontend by Than McIntosh adds some
debugger-callable AST dump functions, similar to function like
debug_tree or debug_rtx. They are all named debug_go_xxx.
Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. Committed
to mainline.
Ian
Index: gcc/go/gofrontend/MERGE
==
On Mon, Feb 18, 2019 at 02:23:34PM +0100, Martin Liška wrote:
>
> As I installed all needed patches, I'm sending a documentation entry
> for the new functionality.
>
> Thoughts?
See below. Ok to commit with suggested changes.
> Thanks,
> Martin
> >From 2d304e3b1d734548811f963c5bed1855b5375c43
On 2/18/19 12:48 AM, Janne Blomqvist wrote:
On Sun, Feb 17, 2019 at 8:19 PM Thomas Koenig wrote:
Hello world,
the attached patch fixes a rather bad ABI violation on POWER systems.
...
I agree, although we're close to the GCC-9 release, it's better to get
this in now. So Ok.
I wonder if we
On Tue, 19 Feb 2019, Martin Sebor wrote:
> Sure, the text is in a section named Program startup, but that doesn't
> imply that the constraints apply only at program startup. If they did,
I think it's clear from the context that the section is describing the
interface between the program and its
> Doesn't the frame have to be laid out correctly during the final reload
> subpass anyway, in order to get the right elimination choices and
> elimination offsets? If so, I'm not sure what the " &&
> info->reload_completed" check in rs6000_stack_info achieves. It seems like
> that's at least par
Hi Paul,
On Tue, Feb 19, 2019 at 10:10:38AM -0600, Paul Clarke wrote:
> Incorrect type for interpreting the result from mfvsrd instruction leads
> to incorrect results. Also, mfvsrd instruction only works as expected in
> 64-bit mode or for 32-bit quantities in 32-bit mode. A more general,
> if
On Tue, Feb 19, 2019 at 1:57 AM Richard Biener wrote:
>
> Looks like vtv_generate_init_routine calls symtab->process_new_functions
> () which has seriously bad effects on GCCs internal memory state.
>
> VTV has zero testsuite coverage it seems and besides its initial
> commit didn't receive any l
On 2/18/19 4:12 PM, Joseph Myers wrote:
On Sat, 16 Feb 2019, Jakub Jelinek wrote:
Hi!
Both the C and C++ standard guarantee that the argc argument to main is
non-negative, the following patch sets (or adjusts) the corresponding
SSA_NAME_RANGE_INFO. While main is just one, with IPA VRP it can
Revision 256615 (SVE unwinding) renamed _UnwindGetGR function
argument, but forgot to update part under #ifdef DWARF_ZERO_REG.
2019-02-19 Uroš Bizjak
* unwind-dw2.c (_Unwind_GetGR) [DWARF_ZERO_REG]: Compare
regno instead of index to DWARF_ZERO_REG.
Bootstrapped on alphaev68-linux-gnu
Test FAILS: sse2-cvtpd2dq-1, sse2-cvtpd2ps, sse2-cvttpd2dq on powerpc64
(big-endian).
_mm_cvtpd_epi32, _mm_cvtpd_ps, _mm_cvttpd_epi32: Type conversion from
vector doubleword type to vector word type leaves the results in even
lanes in big endian mode.
Test FAILS: sse-cvtss2si-1, sse-cvtss2si-2, s
Hi Chung-Lin!
On Tue, 22 Jan 2019 13:16:37 +0100, I wrote:
> On Mon, 14 Jan 2019 21:56:05 +0800, Chung-Lin Tang
> wrote:
> > this version of the wait-clause-with-no-args patch revises the following:
> Thanks.
>
> > Hope this is now okay for trunk when appropriate.
>
> Given that this is a wro
On Fri, Feb 15, 2019 at 12:49:58PM +0100, Martin Jambor wrote:
> Ping please, the issue is now PR 89302.
Please add the PR line to the ChangeLog entry.
> > 2019-02-01 Martin Jambor
> >
> > * omp-general.c (omp_extract_for_data): Removed a duplicate call
> > to omp_adjust_for_condition,
Although the gc toolchain requires POWER8, gccgo does not. This libgo
patch removes a check that POWER8 is required. This fixes GCC PR
89169. Bootstrapped and tested on x86_64-pc-linux-gnu and
ppc64-linux-gnu. Committed to mainline.
Ian
Index: gcc/go/gofrontend/MERGE
==
This libgo patch by Cherry Zhang stops the stack scan when the stack
can not be unwound. In a signal-triggered stack scan, if the signal
is delivered at certain bad time (e.g. in vdso, or in the middle of
setcontext?), the unwinder may not be able to unwind the whole stack,
while it still reports
On Tue, Feb 19, 2019 at 2:49 PM H.J. Lu wrote:
>
> ix86_fpmath should be set to combination of FPMATH_387 and FPMATH_SSE.
> When SSE is disabled, it should be set to FPMATH_387 and 387 codegen is
> also controlled by -msoft-float.
>
> gcc/
>
> PR target/89397
> * config/i386/i386.c
Hi!
On Tue, Feb 19, 2019 at 03:38:56AM -0600, Li Jia He wrote:
> GCC revision 259524 implemented range check for the vec_splat_{su}{8,16,32}
> builtins. However, as a consequence of the implementation, the range check
> is not done correctly for the expected vspltis[bhw] instructions. The result
On Mon, Feb 18, 2019 at 03:01:14PM -1000, Jason Merrill wrote:
> But it's not clear to me that the standard actually allows this. I don't
> think changing the active member of a union in the mem-initializer for
> another member is reasonable.
There is in [expr.const]/2:
an lvalue-to-rvalue conve
ix86_fpmath should be set to combination of FPMATH_387 and FPMATH_SSE.
When SSE is disabled, it should be set to FPMATH_387 and 387 codegen is
also controlled by -msoft-float.
gcc/
PR target/89397
* config/i386/i386.c (ix86_option_override_internal): Set
opts->x_ix86_fpmat
Hi,
On Tue, Feb 19 2019, Martin Liška wrote:
> On 2/14/19 11:19 AM, Jan Hubicka wrote:
>>
...
>> Next stage1 we should also teach the callback to ignore edges of calls
>> that are not being optimized.
>
> I'm sending patch for that.
...
> gcc/ChangeLog:
>
> 2019-02-19 Martin Liska
>
>
On Fri, 15 Feb 2019, Sam Tebbs wrote:
> I was looking into this and it seems that the CPU and architecture
> removals have already been documented in the Arm-specific section of the
> GCC 9 changes, so explicitly mentioning that the documentation has been
> removed as well is probably unnecessar
Hi Ian,
> On Mon, Feb 18, 2019 at 2:48 AM Rainer Orth
> wrote:
>>
>> > The code was already calling syscall, it was just doing it in a way
>> > that the types didn't necessarily match the C declaration. This is
>> > the implementation of Go's syscall.Syscall function, so there isn't
>> > really
Hi Iain,
>> Thanks. This will have to wait for
>>
>> [libphobos] Use sections_elf_shared.d on Solaris 11.5 (PR d/88150)
>> https://gcc.gnu.org/ml/gcc-patches/2019-01/msg01661.html
>
> I'll make a fork of sections support tonight, as that seems to be the
> right way forwards.
>
> O
Adding so that the DIEs of unused external variables can be removed from the
output when
using -feliminate-unused-debug-symbols.
Tested on x86_64-elf, aarch64-elf, powerpc-eabi, powerpc64-elf and arm-eabi.
2019-02-18 Johan Karlsson
PR debug/86964
* dwarf2out.c (premark_used_v
Eric Botcazou writes:
> Hi,
>
> this is a regression present on all active branches since the controversial
> get_initial_register_offset stuff was added to rtlanal.c some time ago, and
> visible in the testsuite on PowerPC/Linux under the form of gnat.dg/opt73.adb
> timing out at run time.
>
>
Hi Iain,
> On Tue, 29 Jan 2019 at 15:44, Rainer Orth
> wrote:
>>
>> Yet another trivial fix for a Solaris libphobos testsuite failure:
>>
>> FAIL: libphobos.shared/load.d -shared-libphobos -ldl (test for excess errors)
>> Excess errors:
>> /vol/gcc/src/hg/trunk/local/libphobos/testsuite/libphobo
The following limits mpfr operations to the maximum exponent range as
determined by available float modes. This avoids excessive work
for evaluating functions like ctan for large arguments.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to trunk.
Richard.
2019-02-19 Richard Bie
On 2/14/19 11:19 AM, Jan Hubicka wrote:
>> Hi.
>>
>> This is patch candidate I created and tested. It's not adding
>> filtering based on opt_for_fn which I would defer to the next
>> stage1.
>>
>> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>>
>> Ready to be installed?
>>
On Tue, 19 Feb 2019 at 10:32, Rainer Orth wrote:
>
> Hi Iain,
>
> > On Tue, 29 Jan 2019 at 13:35, Rainer Orth
> > wrote:
> >>
> >> With the set of libphobos Solaris patches just posted, it would become
> >> possible to enable libphobos on Solaris 11/x86 by default.
> >>
> >> This is what this pa
Hi,
This patch fixes a broken test case I added in a recent patch:
https://gcc.gnu.org/ml/gcc-patches/2019-01/msg01504.html
The broken test can segfault due to writing to read-only memory, which
this new version avoids. Will apply to the openacc-gcc-8-branch shortly.
Thanks,
Gergö
li
Hi,
On 19/02/19 02:39, Jason Merrill wrote:
On 2/18/19 3:15 PM, Paolo Carlini wrote:
Hi,
On 19/02/19 00:52, Jason Merrill wrote:
On 2/18/19 12:14 PM, Paolo Carlini wrote:
Hi Jason,
On 18/02/19 19:28, Jason Merrill wrote:
On 2/18/19 5:31 AM, Paolo Carlini wrote:
Hi Jason,
On 18/02/19 10:2
On Tue, 19 Feb 2019 at 10:28, Christophe Lyon
wrote:
>
> On Mon, 18 Feb 2019 at 21:12, Rainer Orth
> wrote:
> >
> > Hi Christophe,
> >
> > > dg-extract-results currently moves lines like
> > > WARNING: program timed out
> > > at the end of each .exp section when it generates .sum files.
> > >
>
On Mon, Feb 18, 2019 at 7:37 PM H.J. Lu wrote:
>
> On x86-64, since __m64 is returned and passed in XMM registers, we can
> emulate MMX intrinsics with SSE instructions. To support it, we added
>
> #define TARGET_MMX_WITH_SSE (TARGET_64BIT && TARGET_SSE2)
>
> ;; Define instruction set of MMX inst
Looks like vtv_generate_init_routine calls symtab->process_new_functions
() which has seriously bad effects on GCCs internal memory state.
VTV has zero testsuite coverage it seems and besides its initial
commit didn't receive any love.
Can we rip it out please?
Is the patch OK? (Pointless) b
On 2/18/19 8:34 PM, Jason Merrill wrote:
> Fixed thus:
Works for me, thanks!
Martin
Hi,
GCC revision 259524 implemented range check for the vec_splat_{su}{8,16,32}
builtins. However, as a consequence of the implementation, the range check
is not done correctly for the expected vspltis[bhw] instructions. The result
is that we may not get a valid error message if the valid range
Hi Iain,
> On Tue, 29 Jan 2019 at 13:35, Rainer Orth
> wrote:
>>
>> With the set of libphobos Solaris patches just posted, it would become
>> possible to enable libphobos on Solaris 11/x86 by default.
>>
>> This is what this patch does.
>>
>> * It uses a LIBPHOBOS_SUPPORTED variable both in topl
On Mon, 18 Feb 2019 at 21:12, Rainer Orth wrote:
>
> Hi Christophe,
>
> > dg-extract-results currently moves lines like
> > WARNING: program timed out
> > at the end of each .exp section when it generates .sum files.
> >
> > This is because it sorts its output based on the 2nd field, which is
> >
Hi Iain,
> On Tue, 27 Nov 2018 at 23:28, Rainer Orth
> wrote:
>>
>> As mentioned in passing in PR d/87864, libgphobos.so currently fails to
>> link before Solaris 11.4. Until then, you needed to link with -lsocket
>> -lnsl for the networking functions, in S11.4 they were merged into libc.
>>
>>
> So, barring the removal of the get_initial_register_offset stuff, the only
> simple fix is probably to prevent it from calling into the back-end too
> early, for example with the attached fixlet. Tested on x86-64 and
> PowerPC/Linux.
>
> Thoughts? Where do we want to fix this?
>
>
> *
Hi Thomas,
That's just the job. OK for trunk.
Thanks for the quick fix.
Paul
On Mon, 18 Feb 2019 at 22:03, Thomas Koenig wrote:
>
> Hello world,
>
> this patch fixes the 9 regression in C interop with contiguous
> arguments recently reported by Reinhold Bader.
>
> ChangeLog and patch say it al
On Tue, Feb 19, 2019 at 02:52:54AM +, Jonathan Wakely wrote:
> On 18/02/19 21:22 +0100, Jakub Jelinek wrote:
> > On Mon, Feb 18, 2019 at 09:15:39PM +0100, Rainer Orth wrote:
> > > 2019-02-15 Rainer Orth
> > >
> > > * g++.dg/torture/pr89303.C (bad_weak_ptr): Rename to
> > > bad_weak_ptr_
69 matches
Mail list logo
