This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

[PATCH GCC]Obvious change, dump min_profitable_estimate, rather than min_profitable_iters

From: Bin Cheng <Bin dot Cheng at arm dot com>
To: "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
Cc: nd <nd at arm dot com>
Date: Mon, 22 Feb 2016 11:10:55 +0000
Subject: [PATCH GCC]Obvious change, dump min_profitable_estimate, rather than min_profitable_iters
Authentication-results: sourceware.org; auth=none
Nodisclaimer: True
Spamdiagnosticmetadata: NSPM
Spamdiagnosticoutput: 1:23

Hi,
This is an obvious change to vect_estimate_min_profitable_iters.  Given the context, it should dump min_profitable_estimate at patch site, rather than min_profitable_iters.  Or I must mis-understood something in the code.
Build successfully, no test needed.  Is it OK?  I am not sure obvious change rule can be applied during stage4 or not.

Thanks,
bin

2016-02-22  Bin Cheng  <bin.cheng@arm.com>

	* tree-vect-loop.c (vect_estimate_min_profitable_iters): Dump
	min_profitable_estimate, rather than min_profitable_iters.

Attachment: dump-typo-min_profitable_estimate-20160219.txt
Description: dump-typo-min_profitable_estimate-20160219.txt

Follow-Ups:
- Re: [PATCH GCC]Obvious change, dump min_profitable_estimate, rather than min_profitable_iters
  - From: Richard Biener

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]