into stage1 and after somehow fixing PR90040 issue
I will introduce updated patchset described here:
https://gcc.gnu.org/ml/gcc-patches/2017-02/msg01647.html
(the set is supported locally on all branches since 4.9 with making a
lot of regtesting).
Regarding the modulo scheduling maintainership
On Tue, 2 Feb 2010, Cameron Lowell Palmer wrote:
Does Modulo Scheduling work on x86 platforms? I have tried adding in
various versions of the -fmodulo-sched option and get the exact same
output with or without. The application is a very simplistic matrix
multiply without dependencies.
No
Does Modulo Scheduling work on x86 platforms? I have tried adding in
various versions of the -fmodulo-sched option and get the exact same
output with or without. The application is a very simplistic matrix
multiply without dependencies.
Thank you,
Cameron Palmer
l, not many loops are candidates for software pipelining.
Thanks.
>
I would suggest to check the actual compile-time and memory usage, and try
to reduce them later if needed. Modulo-scheduling is not a compile-time
cheap optimization in general.
Ayal.
> Cheers,
> Bingfeng
>
> >
On Fri, Jan 30, 2009 at 7:44 AM, Bingfeng Mei wrote:
> Hello,
> I try to make modulo scheduling work more efficiently for our VLIW target. I
> found one serious issue that prevents current SMS algorithm from achieving
> high IPC is so-called "transitive closure" problem, w
"Bingfeng Mei" wrote on 30/01/2009 14:44:01:
> Hello,
> I try to make modulo scheduling work more efficiently for our VLIW
target. I
> found one serious issue that prevents current SMS algorithm from
achieving
> high IPC is so-called "transitive closure" pro
Hello,
I try to make modulo scheduling work more efficiently for our VLIW target. I
found one serious issue that prevents current SMS algorithm from achieving high
IPC is so-called "transitive closure" problem, where scheduling window is only
calculated using direct predecessors and
[EMAIL PROTECTED] wrote on 17/10/2008 16:36:32:
> Hello,
> I tried to enable modulo scheduling for our target VLIW. It fails even
for the
> simplest loop. I would like to have a look at how GCC produces schedule
for
> other targets. I know that modulo scheduling relies on doloop_en
Hello,
I tried to enable modulo scheduling for our target VLIW. It fails even for the
simplest loop. I would like to have a look at how GCC produces schedule for
other targets. I know that modulo scheduling relies on doloop_end pattern to
identify a pipelineable loop. There are only a handful
[EMAIL PROTECTED] wrote on 18/08/2007 03:19:48:
> I noticed that gcc.dg/sms-antideps.c is failing on my IA64 Linux and
> HP-UX platforms. The failure is:
>
> x.c: In function 'foo':
> x.c:25: internal compiler error: in gen_sub2_insn, at optabs.c:4640
> Please submit a full bug report,
> with p
Steve Ellcey <[EMAIL PROTECTED]> writes:
> I noticed that gcc.dg/sms-antideps.c is failing on my IA64 Linux and
> HP-UX platforms. The failure is:
>
> x.c: In function 'foo':
> x.c:25: internal compiler error: in gen_sub2_insn, at optabs.c:4640
> Please submit a full bug report,
> with preproces
I noticed that gcc.dg/sms-antideps.c is failing on my IA64 Linux and
HP-UX platforms. The failure is:
x.c: In function 'foo':
x.c:25: internal compiler error: in gen_sub2_insn, at optabs.c:4640
Please submit a full bug report,
with preprocessed source if appropriate.
See http://gcc.gnu.org/bugs.h
Hello,
I wanted to update the status of the first patch that
Vladimir had posted to improve modulo-schedualing.
(http://gcc.gnu.org/ml/gcc-patches/2007-01/msg01468.html).
I tested this patch on ppc64 and currently there is one difference in
one of the fortran's testcases (forall_10.f90); this te
gnu.org/ml/gcc/2006-11/msg00361.html:
> We also plan to fix swing modulo scheduling to make it work on ia64
> and improve it by propagating data dependency information to RTL. We
> plan to discuss this project on the GCC mailing list in a few weeks.)
Vladimir & Dorit
14 matches
Mail list logo
