From: William Tambe <tambewilliam@gmail.com>
To: gcc-help <gcc-help@gcc.gnu.org>
Subject: define_cpu_unit syntax clarification
Date: Tue, 31 Jan 2023 12:00:32 -0600 [thread overview]
Message-ID: <CAF8i9mN+VHxeL9470QdwcUd=WwXUgr-us_uUcou-NM0u0-3JzQ@mail.gmail.com> (raw)
Is the following functional unit description using 3 separate
define_cpu_unit constructs:
(define_cpu_unit "slot0" "bfin")
(define_cpu_unit "slot1" "bfin")
(define_cpu_unit "slot2" "bfin")
the same thing as using a single define_cpu_unit construct ?
(define_cpu_unit "slot0,slot1,slot2" "bfin")
Does the order in which define_cpu_unit are used matters ?
reply other threads:[~2023-01-31 18:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAF8i9mN+VHxeL9470QdwcUd=WwXUgr-us_uUcou-NM0u0-3JzQ@mail.gmail.com' \
--to=tambewilliam@gmail.com \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).