> I have addressed all your comments in this revised patch, PFA and inlined
> below.
>
> Is it ok for trunk?
>
> Thanks and Regards,
> Tejas
>
> gcc/ChangeLog:
>
> * gcc/common/config/i386/i386-common.cc (processor_alias_table):
> Use CPU_ZNVER4 for znver4.
> * config/i386/i
On Wed, Nov 16, 2022 at 2:13 PM Alexander Monakov
wrote:
>
> On Wed, 16 Nov 2022, Jan Hubička wrote:
>
> > This looks really promising. I will experiment with the patch for
> separate
> > znver3 model, but I think we should be able to keep
> > them unified and hopefully get both less code duplic
Hello,
On Wed, Nov 16, 2022 at 12:53 PM Kumar, Venkataramanan <
venkataramanan.ku...@amd.com> wrote:
> [AMD Official Use Only - General]
>
> Hi,
>
>
> > Top znver table sizes in insn-automata.o:
> >
> > Before:
> >
> > 30056 r znver1_fp_min_issue_delay
> > 120224 r znver1_fp_transitions
>
>
> >
Hello,
thanks for checking the performance. The patch is OK.
Honza
On Mon, Oct 31, 2022 at 11:39 AM Joshi, Tejas Sanjay <
tejassanjay.jo...@amd.com> wrote:
> [Public]
>
> Hi,
>
> > It is not latency. It is reciprocal throughput. For example, the
> multiplication instruction has
> > latency 3 and
On Mon, Oct 24, 2022 at 4:26 PM Alexander Monakov
wrote:
> > > > This grew insn-automata.cc from 201502 lines to 639968 lines and the
> > > > build of the automata (genautomata) to several minutes in my dev
> tree.
> > >
> > > Yeah, in my unoptimized non-bootstrapped development tree genautomata
