This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Potentially merging the transactional-memory branch into mainline.
On Wed, Nov 02, 2011 at 12:05:43PM -0500, Aldy Hernandez wrote:
>
> >I remember at least seeing middle-end pieces in alias analysis.
>
> Yes, but they're mechanical changes. Do you mean these?:
>
> @@ -1182,6 +1182,8 @@ ref_maybe_used_by_call_p_1 (gimple call,
> case BUILT_IN_MEMPCPY:
> case BUILT_IN_STPCPY:
> case BUILT_IN_STPNCPY:
> + case BUILT_IN_TM_MEMCPY:
> + case BUILT_IN_TM_MEMMOVE:
>
> etc, etc.
>
> >I'd like to see some breakdown into subsystem patches. Can someone provide
> >those together with changelog entries?
>
> I've done another merge this morning, and here is the master
> patchset divided up by subsystems. ChangeLog entries at the top.
> Testsuite changes at the bottom:
>
> http://quesejoda.com/redhat/tm-branch-diffs-from-trunk-at-180744/
>
> p.s. libstdc++-v3 changelog entries are actually in the toplevel
> ChangeLog.tm. I can move these if it bothers someone.
Could you please fix up whitespace in the patch, at least leading tabs
and trailing whitespace?
On the patch it is easy to do, something like:
sed 's/^+\([\t]*\) \{64\}/+\1\t\t\t\t\t\t\t\t/;s/^+\([\t]*\) \{32\}/+\1\t\t\t\t/;s/^+\([\t]*\) \{16\}/+\1\t\t/;s/^+\([\t]*\) \{8\}/+\1\t/;s/^+\(.*[^[:blank:]]\)[[:blank:]]\+$/+\1/;s/^+[[:blank:]]\+$/+/' patch > patch.whitespace
and then interdiff patch patch.whitespace > whitespace
and review that diff and if appropriate commit to branch before merging?
Jakub