From: Vladimir Yakovlev <vbyakovl23@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Uros Bizjak <ubizjak@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: [RFC, x86] Changes for AVX and AVX2 processors
Date: Fri, 11 Jan 2013 11:25:00 -0000 [thread overview]
Message-ID: <CAK1BsWq7fEP=ttLVWo9w6D235JO7d568vSpDL_2EpAxVipUCqQ@mail.gmail.com> (raw)
In-Reply-To: <20130110113139.GX7269@tucnak.redhat.com>
I've fixed Changelog. Can we commit the patch to trunk now?
2012-12-27 Vladimir Yakovlev <vladimir.b.yakovlev@intel.com>
* config/i386/i386-c.c (ix86_target_macros_internal): New case.
(ix86_target_macros_internal): Likewise.
* config/i386/i386.c (m_CORE2I7): Removed.
(m_CORE_HASWELL): New macro.
(m_CORE_ALL): Likewise.
(initial_ix86_tune_features): m_CORE2I7 is replaced by m_CORE_ALL.
(initial_ix86_arch_features): Likewise.
(processor_target_table): Initializations for Core avx2.
(cpu_names): New names "core-avx2".
(ix86_option_override_internal): Changed PROCESSOR_COREI7 by
PROCESSOR_CORE_HASWELL.
(ix86_issue_rate): New case.
(ia32_multipass_dfa_lookahead): Likewise.
(ix86_sched_init_global): Likewise.
* config/i386/i386.h (TARGET_HASWELL): New macro.
(target_cpu_default): New TARGET_CPU_DEFAULT_haswell.
(processor_type): New PROCESSOR_HASWELL.
2013/1/10 Jakub Jelinek <jakub@redhat.com>:
> On Thu, Jan 10, 2013 at 12:28:24PM +0100, Uros Bizjak wrote:
>> On Thu, Jan 10, 2013 at 12:12 PM, Vladimir Yakovlev
>> <vbyakovl23@gmail.com> wrote:
>>
>> > It seems I didn't sent a patch with last changes. Sorry if so.
>> >
>> > Vladimir
>> >
>> > 2012-12-27 Vladimir Yakovlev <vladimir.b.yakovlev@intel.com
>
> Missing > at the end of line.
>
>> >
>> > * config/i386/i386-c.c (ix86_target_macros_internal): New case.
>> > (ix86_target_macros_internal): Likewise.
>
> There is some additional space at the beginning of this line (note, all
> ChangeLog lines but the one with date should be tab indented, not space).
>
> Jakub
next prev parent reply other threads:[~2013-01-11 11:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 13:36 Uros Bizjak
2012-12-29 5:26 ` Vladimir Yakovlev
2012-12-29 10:07 ` Uros Bizjak
[not found] ` <CAK1BsWpUdUg+ivi7pFdbUr8R45YjhbBCNhmN=98sMmW99dy-tg@mail.gmail.com>
2012-12-29 16:57 ` Vladimir Yakovlev
2012-12-30 13:21 ` Uros Bizjak
2012-12-30 16:05 ` Vladimir Yakovlev
2012-12-30 18:05 ` Uros Bizjak
2013-01-10 11:12 ` Vladimir Yakovlev
2013-01-10 11:28 ` Uros Bizjak
2013-01-10 11:31 ` Jakub Jelinek
2013-01-11 11:25 ` Vladimir Yakovlev [this message]
2013-01-11 11:27 ` Jakub Jelinek
2013-01-11 12:15 ` Vladimir Yakovlev
2013-01-11 12:21 ` Uros Bizjak
2013-01-11 12:38 ` Vladimir Yakovlev
2013-01-15 10:08 ` Kirill Yukhin
2012-12-30 11:59 ` Uros Bizjak
-- strict thread matches above, loose matches on Subject: below --
2012-12-27 17:07 Vladimir Yakovlev
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='CAK1BsWq7fEP=ttLVWo9w6D235JO7d568vSpDL_2EpAxVipUCqQ@mail.gmail.com' \
--to=vbyakovl23@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=ubizjak@gmail.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).