Prathamesh Kulkarni writes:
> On Sat, 19 Oct 2019 at 23:45, Richard Sandiford
> wrote:
>>
>> Prathamesh Kulkarni writes:
>> > Hi Richard,
>> > Sorry for not adding the test in PR91532 fix.
>> > Is the attached patch OK to commit ?
>> >
>> > Thanks,
>> > Prathamesh
>> >
>> > 2019-10-18 Prathames
On October 20, 2019 2:54:48 PM GMT+02:00, Richard Sandiford
wrote:
>Richard Biener writes:
>> On October 19, 2019 5:06:40 PM GMT+02:00, Richard Sandiford
> wrote:
>>>After the previous patch, it seems more natural to apply the
>>>PARAM_SLP_MAX_INSNS_IN_BB threshold as soon as we know what
>>>the
On October 20, 2019 3:21:32 PM GMT+02:00, Richard Sandiford
wrote:
>Now that we're keeping multiple vec_infos around at the same time,
>it seemed worth turning current_vector_size into a vec_info field.
>This for example simplifies the book-keeping in vect_analyze_loop
>and helps with some follow
On Mon, Oct 21, 2019 at 1:15 AM Gerald Pfeifer wrote:
>
> On Fri, 11 Oct 2019, liuho...@gcc.gnu.org wrote:
> > commit 63fbcfeaf27d9dd2083ccbd34bdff8fccb63949c
> > Author: liuhongt
> > Date: Fri Oct 11 14:27:47 2019 +0800
> >
> > Update gcc10 changes with new intel ISA.
>
> I just applied th
On 10/5/19 9:24 AM, Jakub Jelinek wrote:
> On Sat, Oct 05, 2019 at 06:12:37AM +, Bernd Edlinger wrote:
>> On 10/3/19 5:25 PM, Jakub Jelinek wrote:
>>> Does this affect debuggability of --enable-checking=yes,rtl compilers?
>>> I mean, often when we replace some macros with inlines step in GDB
>>
On 10/20/19 11:14 AM, Bernd Edlinger wrote:
Hi,
I've noticed that the description of -fcommon that gets printed
with "gcc -v --help" is exactly the opposite of what this
option actually does.
With -fcommon, different global variables w/o initial value
are plced in common blocks, similar to fort
Committed.
Gerald
- Log -
commit 7d0ef4e2d84d051e0764ca2236f20b1de7970b4a
Author: Gerald Pfeifer
Date: Sun Oct 20 22:07:54 2019 +0200
hboehm.info now defaults to https.
diff --git a/htdocs/codingconventions.html b/htdocs/cod
Committed.
Gerald
2019-10-20 Gerald Pfeifer
* doc/install.texi (Configuration, --enable-objc-gc): hboehm.info
now defaults to https.
Index: doc/install.texi
===
--- doc/install.texi(revision 277213)
+++ doc/i
Hi,
this fixes an issue with the gdb step-over aka. "n" command.
It can be seen when you debug an optimized stage-3 cc1
it does not affect -O0 code, though.
This example debug session will explain the effect.
(gdb) b get_alias_set
Breakpoint 5 at 0xa099f0: file ../../gcc-trunk/gcc/alias.c, line
On Sun, Oct 20, 2019 at 1:24 PM Jakub Jelinek wrote:
>
> Hi!
>
> As mentioned in the PR, the x86 backend has various define_insn_and_split
> patterns that are meant to match usually during combine, are then
> unconditionally split during split1 pass and as they have &&
> can_create_pseudo_p ()
>
On Sat, 19 Oct 2019 at 23:45, Richard Sandiford
wrote:
>
> Prathamesh Kulkarni writes:
> > Hi Richard,
> > Sorry for not adding the test in PR91532 fix.
> > Is the attached patch OK to commit ?
> >
> > Thanks,
> > Prathamesh
> >
> > 2019-10-18 Prathamesh Kulkarni
> >
> > PR tree-optimiza
On Mon, 9 Sep 2019, Jose E. Marchesi wrote:
> I just committed the port to svn trunk, in a single commit, yay!
Congratulations!
> Many thanks to you, richard, seguer and the other reviewers for the
> great feedback and suggestions. What got committed is certainly WAY
> better than what I submitt
On Thu, 10 Oct 2019, H.J. Lu wrote:
> Here is the same patch for git repo. Is it OK?
Has this been available since GCC 9.1, or has it been added later?
(If the latter, please add this to a GCC 9.2 or GCC 9.3 section in
that file).
Ok.
Gerald
On Fri, 11 Oct 2019, liuho...@gcc.gnu.org wrote:
> commit 63fbcfeaf27d9dd2083ccbd34bdff8fccb63949c
> Author: liuhongt
> Date: Fri Oct 11 14:27:47 2019 +0800
>
> Update gcc10 changes with new intel ISA.
I just applied this follow-up patch which adds markup. Usually we
also refer to "comman
Hi,
I've noticed that the description of -fcommon that gets printed
with "gcc -v --help" is exactly the opposite of what this
option actually does.
With -fcommon, different global variables w/o initial value
are plced in common blocks, similar to fortran named common
blocks, while with -fno-commo
On 10/18/19 9:33 AM, Georg-Johann Lay wrote:
> Here is some more cases fixed for small targets for noise reduction.
>
> Ok to apply?
>
> Johann
>
> gcc/testsuite/
> Fix some fallout for small targets.
>
> PR testsuite/52641
> * gcc.dg/torture/pr86034.c: Use 32-bit base type for a bi
On Wed, 9 Oct 2019, Joseph Myers wrote:
> I've done the move of GCC wwwdocs to git (using the previously posted and
> discussed scripts), including setting up the post-receive hook to do the
> same things previously covered by the old CVS hooks, and minimal updates
> to the web pages dealing wit
On Wed, 9 Oct 2019, js...@gcc.gnu.org wrote:
> +Use "git commit" and "git push origin
> +master" to check in the patch.
I will admit I made a couple of first commits without reading those
details and just used a plain "git push".
Is there any problem with that, any drawback?
Or could we simpli
Committed.
And as a side note, this should be the first commit in the world
of wwwdocs GIT that was properly checked by my bot. :-)
Gerald
commit bf45ac10505f02e59a0dfb13540cc8d7f5a21a68
Author: Gerald Pfeifer
Date: Sun Oct 20 17:54:09 2019 +0200
www.polyhedron.com is now polyhedron.com
On Sat, 19 Oct 2019, Gerald Pfeifer wrote:
> And this makes it a bit nicer (and shorter).
And this makes the anonymous checkout of wwwdocs simple copy&paste.
Commmitted.
Gerald
diff --git a/htdocs/about.html b/htdocs/about.html
index 48918c8..a67e358 100644
--- a/htdocs/about.html
+++ b/htdocs
Hi,
this patch fixes micompilation of babel Jeff wrote me about. Problem is
the array walking in nonoverlapping_refs_since_match_p which gets wrong
the following testcase:
int
main (int argc, char **argv)
{
int c;
unsigned char out[][1] = { {71}, {71}, {71} };
for (int i = 0; i < 3; i++)
Now that all necessary routines have access to the vec_info,
it's trivial to convert current_vector_size to a member variable.
2019-10-20 Richard Sandiford
gcc/
* tree-vectorizer.h (vec_info::vector_size): New member variable.
(vect_update_max_nunits): Update comment.
These 11 patches just pass vec_infos to one routine each. Splitting
them up make it easier to write the changelogs, but they're so trivial
that it seemed better to send them all in one message.
Pass a vec_info to vect_supportable_shift
2019-10-20 Richard Sandiford
gcc/
* tree-vector
Martin Sebor wrote:
> On 10/19/19 2:56 AM, Iain Sandoe wrote:
>> Andreas Schwab wrote:
>>> On Okt 19 2019, Iain Sandoe wrote:
>>>
This test has failed always on Darwin, because Darwin does not mark
entries in string.h with nonnull attributes. Since the purpose of the test
is to
The increase_alignment pass was using get_vectype_for_scalar_type
to get the preferred vector type for each array element type.
This has the effect of carrying over the vector size chosen by
the first successful call to all subsequent calls, whereas it seems
more natural to treat each array type in
Now that we're keeping multiple vec_infos around at the same time,
it seemed worth turning current_vector_size into a vec_info field.
This for example simplifies the book-keeping in vect_analyze_loop
and helps with some follow-on changes.
Tested on aarch64-linux-gnu and x86_64-linux-gnu.
Richard
Richard Biener writes:
> On October 19, 2019 5:06:40 PM GMT+02:00, Richard Sandiford
> wrote:
>>After the previous patch, it seems more natural to apply the
>>PARAM_SLP_MAX_INSNS_IN_BB threshold as soon as we know what
>>the region is, rather than delaying it to vect_slp_analyze_bb_1.
>>(But rat
On Fri, Oct 18, 2019 at 8:49 PM Richard Earnshaw
wrote:
>
>
> This series of patches rewrites all the DImode arithmetic patterns for
> the Arm backend when compiling for Arm or Thumb2 to split the
> operations during expand (the thumb1 code is unchanged and cannot
> benefit from early splitting as
Hi!
As mentioned in the PR, the x86 backend has various define_insn_and_split
patterns that are meant to match usually during combine, are then
unconditionally split during split1 pass and as they have &&
can_create_pseudo_p ()
in their define_insn condition, if they get matched after split1, not
On 19/10/2019 17:31, Segher Boessenkool wrote:
> Hi Richard,
>
> On Fri, Oct 18, 2019 at 08:48:31PM +0100, Richard Earnshaw wrote:
>>
>> This series of patches rewrites all the DImode arithmetic patterns for
>> the Arm backend when compiling for Arm or Thumb2 to split the
>> operations during expa
30 matches
Mail list logo