From: Ian Lance Taylor <iant@google.com>
To: Mahmood Naderan <nt_mahmood@yahoo.com>
Cc: gcc <gcc-help@gcc.gnu.org>
Subject: Re: bdver1 and bdver2
Date: Sat, 16 Jun 2012 18:32:00 -0000 [thread overview]
Message-ID: <mcrmx43yuo8.fsf@dhcp-172-18-216-180.mtv.corp.google.com> (raw)
In-Reply-To: <1339833508.98995.YahooMailNeo@web111702.mail.gq1.yahoo.com> (Mahmood Naderan's message of "Sat, 16 Jun 2012 00:58:28 -0700 (PDT)")
Mahmood Naderan <nt_mahmood@yahoo.com> writes:
> what is the difference between bdver1 and bdver2?
> I can not find the changlog.
The ChangeLog is here:
2011-07-12 Harsha Jagasia <harsha.jagasia@amd.com>
AMD bdver2 Enablement
* config.gcc (i[34567]86-*-linux* | ...): Add bdver2.
(case ${target}): Add bdver2.
* config/i386/driver-i386.c (host_detect_local_cpu): Let
-march=native recognize bdver2 processors.
* config/i386/i386-c.c (ix86_target_macros_internal): Add
bdver2 def_and_undef
* config/i386/i386.c (struct processor_costs bdver2_cost): New
bdver2 cost table.
(m_BDVER2): New definition.
(m_AMD_MULTIPLE): Includes m_BDVER2.
(initial_ix86_tune_features): Add bdver2 tuning.
(processor_target_table): Add bdver2 entry.
(static const char *const cpu_names): Add bdver2 entry.
(ix86_option_override_internal): Add bdver2 instruction sets.
(ix86_issue_rate): Add bdver2.
(ix86_adjust_cost): Add bdver2.
(has_dispatch): Add bdver2.
* config/i386/i386.h (TARGET_BDVER2): New definition.
(enum target_cpu_default): Add TARGET_CPU_DEFAULT_bdver2.
(enum processor_type): Add PROCESSOR_BDVER2.
* config/i386/i386.md (define_attr "cpu"): Add bdver2.
* config/i386/i386.opt ( mdispatch-scheduler): Add bdver2 to
description.
The patch is here:
http://gcc.gnu.org/ml/gcc-patches/2011-07/msg00842.html
If you want more information, you'll have to be specific as to what you
what to know.
Ian
next prev parent reply other threads:[~2012-06-16 18:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-16 7:58 Mahmood Naderan
2012-06-16 18:32 ` Ian Lance Taylor [this message]
2012-06-17 8:04 ` Mahmood Naderan
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=mcrmx43yuo8.fsf@dhcp-172-18-216-180.mtv.corp.google.com \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=nt_mahmood@yahoo.com \
/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).