Hi!
As mentioned in the PR, I'm afraid we can't easily move the scatter/gather
verification from vect_analyze_data_refs to vectorizable_{load,store},
because we need to process_use in between on the gsinfo.offset to determine
what statements need to be vectorized and that can be only determined
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91067
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
Hi!
The following patch implements roughly the
https://gcc.gnu.org/ml/gcc-patches/2019-06/msg01330.html
design for worksharing loops (so far not for composite for simd, that will
be the next larger task).
Bootstrapped/regtested on x86_64-linux and i686-linux, committed to trunk.
2019-07-03
Hi!
The spec says that reductions should be put on combined parallel for
onto the for and shared on parallel. This patch handles just inscan
reductions that way, doing it right for all reductions will be slightly more
work and once it works, will allow even cleanups. But for inscan it has to
be
Hi!
When working on scan, I've noticed I forgot to emit in loops
that use GOMP_loop_start just to allocate some memory also
GOMP_loop_end_nowait to allow destroying of that worksharing structure on
the libgomp side.
Bootstrapped/regtested on x86_64-linux and i686-linux, committed to trunk.
Giuliano,
I asked for some documentation off you related to the RTL passes. Not sure
if you are just hitting bottlenecks in all_rtl_passes or ipa_passes functions
but it seems that the SSA trees and cfgloop.c and cfgloop.h files optimization
passes would still be a issue. Particularly after the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90357
Paul Hua changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
The force_reg in or1k_expand_compare is hard coded for SImode, which is fine as
this used to only be used on SI expands. However, with FP support this will
cause issues. In general we should only force the right hand operand to a
register if its an immediate. This patch adds an condition to
This adds support for OpenRISC hardware floating point instructions.
This is enabled with the -mhard-float option.
Double-prevision floating point operations work using register pairing as
specified in: https://openrisc.io/proposals/orfpx64a32. This has just been
added in the OpenRISC
gcc/ChangeLog:
* config.gcc (or1k*-*-*): Add mrori and mror to validation.
* doc/invoke.texi (OpenRISC Options): Add mrori option, rewrite all
documenation to be more clear.
* config/or1k/elf.opt (mboard=, mnewlib): Rewrite documentation to be
more clear.
Fixes bad assembly logic with software divide as reported by Richard Selvaggi.
Also, add a basic test to verify the soft math works when enabled.
gcc/testsuite/ChangeLog:
PR target/90362
* gcc.target/or1k/div-mul-3.c: New test.
libgcc/ChangeLog:
PR target/90362
Volatile memory does not match the memory_operand predicate. This
causes extra extend/mask instructions instructions when reading
from volatile memory. On OpenRISC loading volatile memory can be
treated the same as regular memory loads which supports combined
sign/zero extends. Fixing this
Hello,
It's been about 2 months since I last sent these patches. Sorry for the delay
I ended up getting side tracked finishing the new OpenRISC architecture spec
revision.
New since v1:
- Changed 64-bit FPU operations to use explicit register pairs as per spec
revision suggested by Richard
Hi Richard,
Thanks very much for reviewing my patch. I'll update it as your comments.
Before sending the next version, I've several questions embedded for further
check.
on 2019/7/2 下午8:43, Richard Biener wrote:
> On Wed, 20 Mar 2019, Kewen.Lin wrote:
>
>> +/* { dg-require-effective-target
On 7/2/19 11:54 AM, Indu Bhagat wrote:
> Ping.
> Can someone please review these patches ? We would like to get the
> support for CTF integrated soon.
I'm not sure there's really even consensus that we want CTF support in
GCC. Though I think that the changes you've made in the last several
weeks
On 1/24/19 12:51 PM, Giuliano Belinassi wrote:
> This patch adds two variables named 'TV_CGRAPH_FUNC_EXPANSION' and
> 'TV_CGRAPH_IPA_PASSES' that count the elapsed time of the functions
> 'expand_all_functions' and 'ipa_passes', respectivelly.
>
> The main point of this is that these functions
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91067
--- Comment #2 from Boris Staletic ---
Created attachment 46549
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46549=edit
Non-preprocessed file
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91067
--- Comment #1 from Boris Staletic ---
Created attachment 46548
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46548=edit
Minimal reproducer - preprocessed with clang
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91067
Bug ID: 91067
Summary: Clang compiler can't link executable if
std::filesystem::directory_iterator is encountered
Product: gcc
Version: 9.0
Status: UNCONFIRMED
This Go frontend patch by Than McIntosh revamps the way the exporter
tracks exported types and imported packages that need to be mentioned
in the export data.
The previous implementation wasn't properly handling the case where an
exported non-inlinable function refers to an imported type whose
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91065
Jorn Wolfgang Rennecke changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91065
--- Comment #2 from Jorn Wolfgang Rennecke ---
Author: amylaar
Date: Wed Jul 3 00:22:53 2019
New Revision: 272954
URL: https://gcc.gnu.org/viewcvs?rev=272954=gcc=rev
Log:
PR testsuite/91065
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91062
Jorn Wolfgang Rennecke changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
---
On Tue, Jul 02, 2019 at 07:36:21PM -0400, Michael Meissner wrote:
> On Mon, Jul 01, 2019 at 04:27:05PM -0500, Segher Boessenkool wrote:
> > The entry before the 8 is split as well. Maybe that should be "4", to
> > stand out? I don't know what works better; your choice.
>
> I'll look into it.
On 6/26/19 2:06 PM, Mark Wielaard wrote:
> Even if there was no, or an empty address list we would try to generate
> and index for the .debug_addr section with -gdwarf-5 and -gsplit-dwarf.
> The skeleton DIE would also get a (dangling) DW_AT_addr_base in that case.
>
> PR debug/90981
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91051
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment
On 6/18/19 2:58 AM, Martin Liška wrote:
> Hi.
>
> The patch is quite obvious, it copies the same what we do in
> another IPA passes.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
> Ready to be installed?
> Thanks,
> Martin
>
> gcc/ChangeLog:
>
> 2019-06-18
On 6/27/19 7:20 AM, Martin Liška wrote:
> On 6/18/19 12:16 PM, Jakub Jelinek wrote:
>> I think any such length changes should be moved after the two punt checks.
>> Move also the len3 setting before the new checks (of course conditional on
>> is_ncmp).
> Ok, I'm sending updated version of the
On Mon, Jul 01, 2019 at 04:27:05PM -0500, Segher Boessenkool wrote:
> The entry before the 8 is split as well. Maybe that should be "4", to
> stand out? I don't know what works better; your choice.
I'll look into it. Note, the length is used in two places. One at the end to
generate the
On 6/28/19 7:39 AM, Claudiu Zissulescu wrote:
> When entering an interrupt, not only the call save registers needs to
> be place on stack but also the call clobbers one. More over, the
> ARC700 return from interrupt instruction needs to be rtie, the same
> like ARCv2 CPUs. While the ARC6xx family
On 7/1/19 4:28 AM, Martin Liška wrote:
> On 6/27/19 7:24 PM, Richard Sandiford wrote:
>> Martin Liška writes:
>>> diff --git a/gcc/config/i386/i386-expand.c b/gcc/config/i386/i386-expand.c
>>> index d50b811d863..1bd251ea8e2 100644
>>> --- a/gcc/config/i386/i386-expand.c
>>> +++
On 7/2/19 3:52 PM, Joern Wolfgang Rennecke wrote:
> Regression tested running plugin.exp testing gcc configured with
> --enable-checking=all (failure fixed),
> --enable-checking=yes, and without --enable-checking (both no change).
>
> pr91065-patch.txt
>
> 2019-07-02 Joern Rennecke
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90883
--- Comment #13 from Jeffrey A. Law ---
Author: law
Date: Tue Jul 2 23:01:53 2019
New Revision: 272949
URL: https://gcc.gnu.org/viewcvs?rev=272949=gcc=rev
Log:
PR tree-optimization/90883
* g++.dg/tree-ssa/pr90883.c: Add -Os.
So a couple of things can come into play that make this test target
dependent.
First, on some targets we emit a loop to zero the objects. Thankfully
we can use -Os which gets us an empty constructor node again. That
seems to make several unhappy targets happy again.
On i?86 (and perhaps other
Vladislav Ivanishin writes:
> Hi!
>
> It is nice to be able to reload the pretty printers and convenience
> functions from gdbhooks.py without exiting GDB: reloading cc1 takes
> several seconds (plus, the debugging session is lost).
>
> Previously:
>
>(gdb) python import imp;
On 7/1/19 7:47 PM, Martin Sebor wrote:
> Attached is a more complete solution that fully resolves the bug
> report by avoiding a warning in cases like:
>
> char a[32], b[8];
>
> void f (void)
> {
> if (strlen (a) < sizeof b - 2)
> snprintf (b, sizeof b, "b=%s", a); // no
David Malcolm writes:
> On Tue, 2019-07-02 at 14:29 +0300, Vladislav Ivanishin wrote:
>> David Malcolm writes:
>>
>> > On Mon, 2019-07-01 at 12:50 +0300, Vladislav Ivanishin wrote:
>> > > Hi!
>> > >
>> > > GDB's Python API provides strip_typedefs method that can be
>> > > instrumental for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91066
Bug ID: 91066
Summary: GCC does not provide XOP functions through
Product: gcc
Version: 8.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91065
Jorn Wolfgang Rennecke changed:
What|Removed |Added
Keywords||patch
--- Comment #1 from Jorn
Regression tested running plugin.exp testing gcc configured with
--enable-checking=all (failure fixed),
--enable-checking=yes, and without --enable-checking (both no change).
2019-07-02 Joern Rennecke
PR testsuite/91065
* testsuite/gcc.dg/plugin/start_unit_plugin.c: Register
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91065
Bug ID: 91065
Summary: gcc.dg/plugin/start_unit_plugin.c uses ggc memory
without registering a root_tab
Product: gcc
Version: 10.0
Status: UNCONFIRMED
On 7/1/19 3:02 AM, Aldy Hernandez wrote:
> As discussed prior. This enforces canonicalization at creation time,
> which makes things a lot more consistent throughout.
>
> Since now [MIN, MAX] will be canonicalized into VR_VARYING, we can no
> longer depend on normalizing VARYING's into [MIN,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78736
--- Comment #10 from Jonny Grant ---
Thank you for adding me to the ticket.
I'll add a bounty of $150 for this feature.
Could Prathamesh's change be incorporated?
Thank you, Jonny
On 6/30/19 3:50 PM, Martin Sebor wrote:
> On 6/26/19 6:11 PM, Jeff Law wrote:
[ Another big snip ]
>
>> Is there a strong need for an overloaded operator? Our guidelines
>> generally discourage operator overloads. This one seems on the border
>> to me. Others may have different ideas where the
On 7/1/19 5:00 AM, Martin Liška wrote:
> Hi.
>
> This is updated version of the zstd patch that should handle all what Joseph
> pointed out.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
> Ready to be installed?
> Thanks,
> Martin
>
>
>
On 7/1/19 5:00 AM, Martin Liška wrote:
> Hi.
>
> This is updated version of the zstd patch that should handle all what Joseph
> pointed out.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
> Ready to be installed?
> Thanks,
> Martin
>
>
>
On 7/1/19 4:59 AM, Martin Liška wrote:
> Hi.
>
> Ok, so there's a version with added ChangeLog that survives regression tests.
>
> Ready to be installed?
> Thanks,
> Martin
>
>
> 0001-Add-.gnu.lto_.lto-section.patch
>
> From e6745583dc4b7f5543878c0a25498e818531f73e Mon Sep 17 00:00:00 2001
>
On 7/1/19 4:59 AM, Martin Liška wrote:
> Hi.
>
> Ok, so there's a version with added ChangeLog that survives regression tests.
>
> Ready to be installed?
> Thanks,
> Martin
>
>
> 0001-Add-.gnu.lto_.lto-section.patch
>
> From e6745583dc4b7f5543878c0a25498e818531f73e Mon Sep 17 00:00:00 2001
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91064
Bug ID: 91064
Summary: __is_standard_layout incorrect for a class with
multiple bases
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90581
qinzhao at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |qinzhao at gcc dot
On 6/28/19 12:46 PM, Richard Sandiford wrote:
> Segher Boessenkool writes:
>> On Fri, Jun 28, 2019 at 08:55:00AM -0600, Martin Sebor wrote:
>>> Jeff reminded me in a code review the other day that GCC does
>>> have a guideline for defining POD structs with the keyword
>>> "struct" and classes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90581
--- Comment #3 from qinzhao at gcc dot gnu.org ---
Author: qinzhao
Date: Tue Jul 2 20:23:30 2019
New Revision: 272948
URL: https://gcc.gnu.org/viewcvs?rev=272948=gcc=rev
Log:
PR preprocessor/90581
Add a cpp option -fmax-include-depth to set the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88059
Martin Sebor changed:
What|Removed |Added
Status|RESOLVED|ASSIGNED
Last reconfirmed|2018-11-16
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83819
Bug 83819 depends on bug 88059, which changed state.
Bug 88059 Summary: Spurious stringop-overflow warning with strlen, malloc and
strncpy
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88059
What|Removed |Added
On 6/29/19 9:51 AM, Segher Boessenkool wrote:
> On Mon, Jun 17, 2019 at 01:13:43PM -0600, Jeff Law wrote:
>>> (Hopefully one day GET_MODE_SIZE & co. will assert on BLKmode and VOIDmode.)
>> Yea. Not sure why. There's probably a compile-time hit, but I suspect
>> it'd turn up some interesting
On 7/1/19 2:52 AM, Aldy Hernandez wrote:
> As discussed before, this enforces types on undefined and varying, which
> makes everything more regular, and removes some special casing
> throughout range handling.
>
> The min/max fields will contain TYPE_MIN_VALUE and TYPE_MAX_VALUE, which
> will
On 7/1/19 3:35 AM, Martin Liška wrote:
> Hi.
>
> The patch is about use-after-scope. However, I can't verify
> it survives bootstrap on the affected target.
>
> Ready for the trunk?
> Thanks,
> Martin
>
> gcc/ChangeLog:
>
> 2019-07-01 Martin Liska
>
> PR target/88056
> *
On 7/2/19 3:59 AM, Richard Biener wrote:
> On Tue, Jul 2, 2019 at 3:48 AM Martin Sebor wrote:
>>
>> Attached is a more complete solution that fully resolves the bug
>> report by avoiding a warning in cases like:
>>
>>char a[32], b[8];
>>
>>void f (void)
>>{
>> if (strlen (a) <
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91063
Bug ID: 91063
Summary: [10 Regression] ICE in set_vinfo_for_stmt, at
tree-vectorizer.c:676
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90393
ensadc at mailnesia dot com changed:
What|Removed |Added
CC||ensadc at mailnesia dot com
On Tue, Jul 2, 2019 at 9:06 PM Jason Merrill wrote:
> On Mon, Jul 1, 2019 at 8:59 PM Paul E. McKenney
> wrote:
> >
> > On Tue, Jul 02, 2019 at 05:58:48AM +0530, Akshat Garg wrote:
> > > On Tue, Jun 25, 2019 at 9:49 PM Akshat Garg wrote:
> > >
> > > > On Tue, Jun 25, 2019 at 4:04 PM Ramana
On 7/2/19 6:36 AM, Giuliano Belinassi wrote:
> This patch makes lto-dump the symtab callgraph in graphviz DOT format.
>
> Previously, the suggested patch had some minor and checkstyle issues
> that were fixed in this version.
>
>
> gcc/ChangeLog
> 2019-07-02 Giuliano Belinassi
>
>
On Tue, Jun 18, 2019 at 8:58 AM H.J. Lu wrote:
>
> On Tue, Jun 11, 2019 at 8:14 AM H.J. Lu wrote:
> >
> > For op_by_pieces operations between two areas of memory, this patch adds
> > -fminimize-op-by-pieces-run to minimize number of operations. When
> > operating on LENGTH bytes of memory, it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91062
--- Comment #1 from Jorn Wolfgang Rennecke ---
Similarly, gcc.dg/torture/ipa-pta-1.c fails four scan tests because
ipa-pta-1.c.083i.pta2 gets corrupted in the ENABLE_GC_ALWAYS_COLLECT scenario.
On Tue, Jul 2, 2019 at 8:40 PM Paul E. McKenney
wrote:
> On Tue, Jul 02, 2019 at 02:15:55PM +0100, Ramana Radhakrishnan wrote:
> > On Tue, Jul 2, 2019 at 1:38 PM Paul E. McKenney
> wrote:
> >
> > >
> > > Once a user-created non-dependent pointer is assigned to, it is OK to
> > > break the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79632
--- Comment #2 from Roland Illig ---
(In reply to Eric Gallager from comment #1)
> What exactly is the harm of the redundancy? I don't think this is too big of
> an issue...
The harm of redundancy is that there is no single point of truth. When
On 7/2/19 6:37 AM, Martin Liška wrote:
> Hi.
>
> The patch is about a new option that can be handy when you pipe
> output and you do not use an object file.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
> Ready to be installed?
> Thanks,
> Martin
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88059
Moritz Bender changed:
What|Removed |Added
CC||molli.bender at gmail dot com
---
On 7/2/19 2:45 AM, Richard Biener wrote:
> External Email
>
> --
> On Mon, Jul 1, 2019 at 11:58 PM Gary Oblock wrote:
>> I've been looking at trying to optimize the performance of code for
>> programs that use functions like
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91033
--- Comment #5 from Jakub Jelinek ---
Created attachment 46546
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46546=edit
gcc10-pr91033.patch
This works though.
On July 2, 2019 5:36:08 PM GMT+02:00, Jason Merrill wrote:
>On Mon, Jul 1, 2019 at 8:59 PM Paul E. McKenney
>wrote:
>>
>> On Tue, Jul 02, 2019 at 05:58:48AM +0530, Akshat Garg wrote:
>> > On Tue, Jun 25, 2019 at 9:49 PM Akshat Garg
>wrote:
>> >
>> > > On Tue, Jun 25, 2019 at 4:04 PM Ramana
On 7/2/19 8:32 AM, Aaron Sawdey wrote:
> This is the second piece for allowing inline expansion of memmove. Now that
> the old movmem patterns have all been renamed to cpymem, the movmem optab can
> be added back.
>
> Next piece will be: add support for __builtin_memmove() to use the movmem
>
Ping.
Can someone please review these patches ? We would like to get the
support for CTF integrated soon.
Thanks
Indu
On Wed, Jun 26, 2019 at 11:38 PM Indu Bhagat wrote:
>
> Hello,
>
> This patch series adds support for CTF generation in GCC.
>
> [Changes from V2]
> - Patch 1, 2, and 3 have
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91062
Bug ID: 91062
Summary: gcc.dg/ipa/ipa-pta-1.c dump contains garbage when gcc
was configured with --enable-checking=all
Product: gcc
Version: 10.0
Status: UNCONFIRMED
On Tue, 2 Jul 2019, Martin Liška wrote:
After the discussion with Richi and Nathan, I made a place in tree_function_decl
and I rebased the original Dominik's patch on top of that.
So, last time there were some questions about the legality of this
transformation. Did you change the exact set
On Tue, Jul 02, 2019 at 05:01:33PM +0200, Christophe Lyon wrote:
> On Mon, 1 Jul 2019 at 17:58, Kyrill Tkachov
> wrote:
> > +static tree
> > +arm_data_attr (tree * node,
> > + tree name,
> > + tree args ATTRIBUTE_UNUSED,
> > + intflags
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91061
Bug ID: 91061
Summary: Enum type libcall_type violates the C++ One Definition
Rule
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
This patch by Cherry Zhang changes the Go frontend to use the builtin
memset function for zeroing a range of memory that doesn't contain any
pointers. Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu.
Committed to mainline.
Ian
2019-07-02 Cherry Zhang
* go-gcc.cc
Hi All,
Here's an updated patch with the changes processed from the previous review.
I've bootstrapped and regtested on aarch64-none-linux-gnu and
x86_64-pc-linux-gnu and no issues.
Ok for trunk?
Thanks,
Tamar
The 07/02/2019 11:20, Richard Biener wrote:
> On Tue, 2 Jul 2019, Tamar Christina
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91033
--- Comment #4 from Jakub Jelinek ---
(In reply to Richard Biener from comment #3)
> 08:57 < richi> jakub: can we delay scatter/gather store recog to
>vectorizable_store/load, thus always detect the dataref
> pattern
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78736
Eric Gallager changed:
What|Removed |Added
CC||jg at jguk dot org
--- Comment #9 from
On 7/2/19 5:49 AM, Martin Liška wrote:
Hi.
After the discussion with Richi and Nathan, I made a place in tree_function_decl
and I rebased the original Dominik's patch on top of that.
Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
FWIW, I think there is a choice
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91058
Tom Smeding changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
Attached patch improves the split condition from using
TARGET_MMX_WITH_SSE to TARGET_SSEx && SSE_REGNO_P, which is what these
splitters really split.
2019-07-02 Uroš Bizjak
* config/i386/mmx.md (mmx_packswb):
Use TARGET_SSE2 && SSE_REGNO_P in split condition.
(mmx_packssdw):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91058
Jonathan Wakely changed:
What|Removed |Added
Keywords||ice-on-valid-code
On 7/2/19 9:01 AM, Christophe Lyon wrote:
Hi Kyrill,
On Mon, 1 Jul 2019 at 17:58, Kyrill Tkachov wrote:
Hi Christophe,
On 6/13/19 4:13 PM, Christophe Lyon wrote:
Hi,
Similar to what already exists for TI msp430 or in TI compilers for
arm, this patch adds support for "noinit" attribute for
On Mon, Jul 1, 2019 at 8:59 PM Paul E. McKenney wrote:
>
> On Tue, Jul 02, 2019 at 05:58:48AM +0530, Akshat Garg wrote:
> > On Tue, Jun 25, 2019 at 9:49 PM Akshat Garg wrote:
> >
> > > On Tue, Jun 25, 2019 at 4:04 PM Ramana Radhakrishnan <
> > > ramana@googlemail.com> wrote:
> > >
> > >> On
Bootstrap and regtest running on x86_64-redhat-linux, s390x-redhat-linux
and ppc64le-redhat-linux.
Currently s390 emits the following sequence to store a frame_pc:
a:
.LASANPC0:
lg %r1,.L5-.L4(%r13)
la %r1,0(%r1,%r12)
stg
David Malcolm writes:
>> Hi David,
>> I can work on to get the SVN commit access.
>> As a maintainer has to sponsor it would you mind being the one?
>
> https://www.gnu.org/software/gcc/svnwrite.html says:
> "a well-established GCC maintainer (including reviewers) can approve
> for write access
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91060
Bug ID: 91060
Summary: [10 regression] gcc.c-torture/execute/scal-to-vec1.c
fails on armeb-none-linux-gnueabihf since r272843
Product: gcc
Version: 10.0
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91059
Bug ID: 91059
Summary: [10 regression]
gcc.c-torture/execute/builtins/snprintf-chk.c fails on
aarch64-elf since r272843
Product: gcc
Version: 10.0
On Tue, Jul 02, 2019 at 02:15:55PM +0100, Ramana Radhakrishnan wrote:
> On Tue, Jul 2, 2019 at 1:38 PM Paul E. McKenney wrote:
>
> >
> > Once a user-created non-dependent pointer is assigned to, it is OK to
> > break the dependency.
>
> Ok, that's good.
> >
> > Or am I missing the point here?
>
Hi Kyrill,
On Mon, 1 Jul 2019 at 17:58, Kyrill Tkachov wrote:
>
> Hi Christophe,
>
> On 6/13/19 4:13 PM, Christophe Lyon wrote:
> > Hi,
> >
> > Similar to what already exists for TI msp430 or in TI compilers for
> > arm, this patch adds support for "noinit" attribute for arm. It's very
> >
Hi David, Andrea,
On 7/2/19 3:46 PM, David Malcolm wrote:
On Wed, 2019-06-26 at 15:05 +, Andrea Corallo wrote:
> David Malcolm writes:
>
> > On Tue, 2019-06-25 at 08:11 +, Andrea Corallo wrote:
> > > Hi,
> > > third version for this patch with the simplified test.
> > >
> > > make
On Wed, 2019-06-26 at 15:05 +, Andrea Corallo wrote:
> David Malcolm writes:
>
> > On Tue, 2019-06-25 at 08:11 +, Andrea Corallo wrote:
> > > Hi,
> > > third version for this patch with the simplified test.
> > >
> > > make check-jit pass clean
> > >
> > > Bests
> > > Andrea
> > >
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91058
Tom Smeding changed:
What|Removed |Added
CC||tom.smeding at gmail dot com
--- Comment
On Tue, 2 Jul 2019 at 12:30, Richard Earnshaw wrote:
>
>
>
> On 02/07/2019 11:13, Richard Earnshaw wrote:
> >
> >
> > On 02/07/2019 09:39, Richard Earnshaw wrote:
> >>
> >>
> >> On 01/07/2019 16:58, Kyrill Tkachov wrote:
> >>> Hi Christophe,
> >>>
> >>> On 6/13/19 4:13 PM, Christophe Lyon wrote:
Hi,
While running the GCC testsuite with an armv8-m target, I noticed that
a few tests where causing the BFD linker to crash. I opened PR
ld/24709 for this [1], but fixing it properly is tricky and not worth
the headache.
I "fixed" the linker so that it emits a useful error message instead
of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91058
Bug ID: 91058
Summary: Crash involving std::variant, std::visit, templates,
and static constexpr
Product: gcc
Version: 7.4.0
Status: UNCONFIRMED
Severity:
This is the second piece for allowing inline expansion of memmove. Now that
the old movmem patterns have all been renamed to cpymem, the movmem optab can
be added back.
Next piece will be: add support for __builtin_memmove() to use the movmem optab
and
associated patterns.
This patch passes
1 - 100 of 193 matches
Mail list logo
