Hi Ramana. You have the following branches remaining on Launchpad:
* lp:~ramana/gcc-linaro/47-lower-subreg-experiments * lp:~ramana/gcc-linaro/47-improve-neon-intrinsics * lp:~ramana/gcc-linaro/47-nobble-promote-mode * lp:~ramana/gcc-linaro/47-smin-umin-idiom
Which are obsolete, which should be spun out into backlog blueprints, and which should be taken over by someone?
-- Michael
-----Original Message----- From: Michael Hope [mailto:michael.hope@linaro.org] Sent: 12 December 2012 22:54 To: Ramana Radhakrishnan Cc: linaro-toolchain@lists.linaro.org Subject: Clearing out past branches
Hi Ramana. You have the following branches remaining on Launchpad:
- lp:~ramana/gcc-linaro/47-lower-subreg-experiments
Obsolete- drop .
- lp:~ramana/gcc-linaro/47-improve-neon-intrinsics
Obsolete - drop.
- lp:~ramana/gcc-linaro/47-nobble-promote-mode
This one didn't do as well as expected as it ended up causing more zero extends than necessary if my memory serves me right. This could be a course for a low priority future blueprint.
- lp:~ramana/gcc-linaro/47-smin-umin-idiom
https://code.launchpad.net/~ramana/gcc-linaro/47-smin-umin-idiom/+merge/1043...
In addition to the backend patch it would be good to implement something similar in tree before the vectorizer kicks in allowing such loops to be vectorized.
Therefore a backlog blueprint is worth it + this patch to the backend being considered for 4.9 time frame.
Regards, Ramana
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
On 13 December 2012 22:22, Ramana Radhakrishnan Ramana.Radhakrishnan@arm.com wrote:
-----Original Message----- From: Michael Hope [mailto:michael.hope@linaro.org] Sent: 12 December 2012 22:54 To: Ramana Radhakrishnan Cc: linaro-toolchain@lists.linaro.org Subject: Clearing out past branches
Hi Ramana. You have the following branches remaining on Launchpad:
- lp:~ramana/gcc-linaro/47-lower-subreg-experiments
Obsolete- drop .
Dropped.
- lp:~ramana/gcc-linaro/47-improve-neon-intrinsics
Obsolete - drop.
Dropped.
- lp:~ramana/gcc-linaro/47-nobble-promote-mode
This one didn't do as well as expected as it ended up causing more zero extends than necessary if my memory serves me right. This could be a course for a low priority future blueprint.
Dropped. This plus flag_ree in the future?
- lp:~ramana/gcc-linaro/47-smin-umin-idiom
https://code.launchpad.net/~ramana/gcc-linaro/47-smin-umin-idiom/+merge/1043...
In addition to the backend patch it would be good to implement something similar in tree before the vectorizer kicks in allowing such loops to be vectorized.
Therefore a backlog blueprint is worth it + this patch to the backend being considered for 4.9 time frame.
Obsoleted and split into: https://launchpad.net/gcc-linaro/+spec/detect-smin-umin-idiom
-- Michael
This one didn't do as well as expected as it ended up causing more
zero extends than necessary if my memory serves me right. This could be a course for a low priority future blueprint.
Dropped. This plus flag_ree in the future?
I'm not so sure that flag_ree will help AArch32 in the future but that is certainly a good topic for investigation.
AFAICS, flag_ree helps with removing unnecessary sign/zero extensions when architectures have a 32 bit register (something like the w* registers on AArch64) written to and a read from the corresponding value zero extended to a 64 bit register ( i.e. the equivalent x register).
So I'd expect flag_ree to remove the redundant zero extension between
Write to w0 Zero_extend Xn from W0. Read from Xn .
Regards Ramana
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
linaro-toolchain@lists.linaro.org