On 8/14/19 1:53 PM, Jeff Law wrote:
On 8/13/19 6:51 PM, Aldy Hernandez wrote:
Presumably this was better than moving the implementation earlier.
Actually, it was for ease of review. I made some changes to the
function, and I didn't want the reviewer to miss them because I had
moved the fun
On 8/13/19 6:51 PM, Aldy Hernandez wrote:
>> Presumably this was better than moving the implementation earlier.
>
> Actually, it was for ease of review. I made some changes to the
> function, and I didn't want the reviewer to miss them because I had
> moved the function wholesale. I can move the
On 8/12/19 7:32 PM, Jeff Law wrote:
On 8/12/19 12:48 PM, Aldy Hernandez wrote:
This is a ping of:
https://gcc.gnu.org/ml/gcc-patches/2019-07/msg8.html
I have addressed the comments Jeff mentioned there.
This patch goes before the VR_VARYING + types patch, but I can adapt
either one to com
On 8/12/19 12:48 PM, Aldy Hernandez wrote:
> This is a ping of:
>
> https://gcc.gnu.org/ml/gcc-patches/2019-07/msg8.html
>
> I have addressed the comments Jeff mentioned there.
>
> This patch goes before the VR_VARYING + types patch, but I can adapt
> either one to come first. I can even mu
This is a ping of:
https://gcc.gnu.org/ml/gcc-patches/2019-07/msg8.html
I have addressed the comments Jeff mentioned there.
This patch goes before the VR_VARYING + types patch, but I can adapt
either one to come first. I can even munge them together into one
patch, if it helps review.
