<div dir="ltr"><div>Dear Duncan,<br><br> thank you very much. I have been able to use it now, via the following command line:<br><br> clang -emit-llvm -c -fstack-protector canary.c -o canary.bc<br> llc -print-before=stack-protector -print-after=stack-protector -o canary.s < canary.bc<br>
</div><div><div> <br>Thank you again,<br><br></div><div>Izabela Maffra.<br></div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On 26 January 2013 15:55, <span dir="ltr"><<a href="mailto:llvmdev-request@cs.uiuc.edu" target="_blank">llvmdev-request@cs.uiuc.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send LLVMdev mailing list submissions to<br>
<a href="mailto:llvmdev@cs.uiuc.edu">llvmdev@cs.uiuc.edu</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:llvmdev-request@cs.uiuc.edu">llvmdev-request@cs.uiuc.edu</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:llvmdev-owner@cs.uiuc.edu">llvmdev-owner@cs.uiuc.edu</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of LLVMdev digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: [cfe-dev] RFC: put commit messages in *-commits subject<br>
lines? (Daniel Dunbar)<br>
2. Re: TargetLowering vs. TargetTransform (Nadav Rotem)<br>
3. Re: [cfe-dev] RFC: put commit messages in *-commits subject<br>
lines? (Sebastian Pop)<br>
4. Re: [cfe-dev] RFC: put commit messages in *-commits subject<br>
lines? (Daniel Dunbar)<br>
5. Re: [cfe-dev] RFC: put commit messages in *-commits subject<br>
lines? (Daniel Dunbar)<br>
6. Re: [cfe-dev] RFC: put commit messages in *-commits subject<br>
lines? (NAKAMURA Takumi)<br>
7. Re: [cfe-dev] RFC: put commit messages in *-commits subject<br>
lines? (Tobias Grosser)<br>
8. Re: [cfe-dev] RFC: put commit messages in *-commits subject<br>
lines? (Daniel Dunbar)<br>
9. Re: [cfe-dev] RFC: put commit messages in *-commits subject<br>
lines? (Eli Bendersky)<br>
10. Re: [cfe-dev] RFC: put commit messages in *-commits subject<br>
lines? (David Blaikie)<br>
11. Re: [cfe-dev] RFC: put commit messages in *-commits subject<br>
lines? (Eli Bendersky)<br>
12. Re: TargetLowering vs. TargetTransform (Renato Golin)<br>
13. Re: [cfe-dev] RFC: put commit messages in *-commits subject<br>
lines? (Tobias Grosser)<br>
14. Re: Testing canaries (Duncan Sands)<br>
15. Re: [cfe-dev] RFC: put commit messages in *-commits subject<br>
lines? (David Blaikie)<br>
16. lli problem with a simple OpenGL (sara.elshobaky)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 25 Jan 2013 14:18:08 -0800<br>
From: Daniel Dunbar <<a href="mailto:daniel@zuster.org">daniel@zuster.org</a>><br>
To: Sebastian Pop <<a href="mailto:spop@codeaurora.org">spop@codeaurora.org</a>><br>
Cc: "<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a> Developers" <<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a>>, Daniel<br>
Dunbar <<a href="mailto:daniel_dunbar@apple.com">daniel_dunbar@apple.com</a>>, LLVM Developers Mailing List<br>
<<a href="mailto:llvmdev@cs.uiuc.edu">llvmdev@cs.uiuc.edu</a>><br>
Subject: Re: [LLVMdev] [cfe-dev] RFC: put commit messages in *-commits<br>
subject lines?<br>
Message-ID:<br>
<<a href="mailto:CAEU8z69eX%2BQQyakoKMK38fGZ9ZN5xOQV_tq%2BHhxGromLOAmsXg@mail.gmail.com">CAEU8z69eX+QQyakoKMK38fGZ9ZN5xOQV_tq+HhxGromLOAmsXg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
On Fri, Jan 25, 2013 at 2:06 PM, Sebastian Pop <<a href="mailto:spop@codeaurora.org">spop@codeaurora.org</a>> wrote:<br>
<br>
> Sebastian Pop wrote:<br>
> > Hi Daniel,<br>
> ><br>
> > Daniel Dunbar wrote:<br>
> > > Hi Sebastion,<br>
> > ><br>
> > > I've attached the current configuration file from the server.<br>
> > ><br>
> > > I'm not sure how far you want to go down the "trying to get realize<br>
> nice<br>
> > > summary path" lines, but if svn_mailer somehow supported running an<br>
> > > external script to process the commit and come up with the path that<br>
> would<br>
> > > be ideal for integration on the server.<br>
> ><br>
> > I think you could modify the sources of svn_mailer to add such a hook.<br>
> When I<br>
> > first investigated this issue, I ended on a bug report from the debian<br>
> project<br>
> > that fixed the subject line with a one line patch:<br>
> ><br>
> > > To get the first line of the log message as a subject line, please<br>
> apply this<br>
> > > one line patch:<br>
> <a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=17;bug=379534" target="_blank">http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=17;bug=379534</a><br>
> > > Note that you can directly patch the installed script: on my machine<br>
> it is<br>
> > > located in<br>
> /usr/local/lib/python2.7/dist-packages/svnmailer/notifier/_mail.py<br>
> ><br>
> > For your convenience, here is the patch from that debian bug report:<br>
> ><br>
> ><br>
> > svnmailer: add log substitution for subject templates<br>
> ><br>
> > Add first line of commit log as a substitution variable for<br>
> > *_subject_template, E.G. add %(log)s to use.<br>
> ><br>
> > Signed-off-by: Peter Korsgaard <<a href="mailto:jacmet@sunsite.dk">jacmet@sunsite.dk</a>><br>
> ><br>
> > Index: svnmailer-1.0.8/src/lib/svnmailer/notifier/_mail.py<br>
> > ===================================================================<br>
> > --- svnmailer-1.0.8.orig/src/lib/svnmailer/notifier/_mail.py 2008-05-27<br>
> 14:56:27.000000000 +0200<br>
> > +++ svnmailer-1.0.8/src/lib/svnmailer/notifier/_mail.py 2008-05-27<br>
> 15:01:50.000000000 +0200<br>
> > @@ -314,6 +314,7 @@<br>
> > 'part' : countprefix,<br>
> > 'files' : self._getPrefixedFiles(changeset),<br>
> > 'dirs' : self._getPrefixedDirectories(changeset),<br>
> > + 'log' : self.getLog().split('\n',1)[0],<br>
> > }<br>
> ><br>
> > # We may try twice, first with files/dirs = files<br>
> ><br>
> ><br>
><br>
> Once you patched the installed version of this file, in<br>
> /usr/local/lib/python2.7/dist-packages/svnmailer/notifier/_mail.py<br>
> you have two more changes in the config file you sent me: (the first<br>
> change to<br>
> print the context of diff is something that I was missing more than the<br>
> subject)<br>
><br>
<br>
I'm a bit hesitant to just hack up the installed copy of svnmailer, are we<br>
sure this patch hasn't been dealt with in an upstream version?<br>
<br>
<br>
><br>
> --- svn-mailer.conf.orig 2013-01-25 15:39:23.000000000 -0600<br>
> +++ svn-mailer.conf 2013-01-25 15:42:02.000000000 -0600<br>
> @@ -1,6 +1,6 @@<br>
> [general]<br>
> sendmail_command = /usr/sbin/sendmail<br>
> -diff_command = /usr/bin/diff -u -L %(label_from)s -L %(label_to)s<br>
> %(from)s %(to)s<br>
> +diff_command = /usr/bin/diff -up -L %(label_from)s -L %(label_to)s<br>
> %(from)s %(to)s<br>
> generate_diffs = add copy modify propchange<br>
><br>
<br>
I'll go ahead and make this change.<br>
<br>
- Daniel<br>
<br>
<br>
><br>
> [authors]<br>
> @@ -360,6 +360,7 @@<br>
> mail_type = single<br>
> show_applied_charset = nondefault<br>
> custom_header = SVN-Repository %(REPOS)s<br>
> +commit_subject_template = %(prefix)s r%(revision)s - %(log)s<br>
><br>
> [branch]<br>
> for_repos = .*/llvm-project$<br>
><br>
><br>
><br>
> Note that I have not addressed the path prefix suggestion from David:<br>
><br>
> >>> For what it's worth, (I think) Chris' suggestion of including the<br>
> >>> directories was about including them "smart"ly by removing conceptual<br>
> >>> duplicates (lib/foo + include/foo + test/foo) and generally giving a<br>
> >>> brief sense of what a change is touching. If the change you have adds<br>
> >>> the full (repo-relative) path all the directories without any smart<br>
> >>> deduplication then I suspect it's going to easily push the log<br>
> >>> description off most mail readers (especially mobile) & reduce the<br>
> >>> value of this change.<br>
> >>><br>
> >>> I suspect we'll want to just stick with revision + log for now.<br>
> >><br>
> >> That's fine. Alternatively we can provide a list of all the dirs that<br>
> we want<br>
> >> to see appearing and match them like this:<br>
> >><br>
> >> for_paths =<br>
> .*(?P<SelectDirs>(lib/Analysis|lib/Transforms/Vectorize|lib/Transforms/Scalar)).*<br>
> >><br>
> >> commit_subject_template = %(prefix)s r%(revision)s - [%(SelectDirs)s]<br>
> %(log)s<br>
> ><br>
> >Could we go one step further and map these paths to names (eg: map<br>
> >"lib/Analysis", "include/llvm/Analysis", "test/Analysis" -> "Analysis"<br>
> >and unique the results)? Also, I'd prefer to have the dirs after the<br>
> >log message I think, though perhaps if we get them short enough it'd<br>
> >work.<br>
> ><br>
> >This solution does seem like it could involve a bit of manual work to<br>
> >update the list of blessed dirs all the time. If we could express it<br>
> >generically (lib/*, test/*, include/llvm/*) it might be OK, but as it<br>
> >stands I'm still not sure it's worth the hassle.<br>
><br>
> This could be done as Daniel has suggested, running a separate script that<br>
> filters and classifies in a smarter way the commits following the paths<br>
> they are<br>
> touching.<br>
><br>
> Thanks,<br>
> Sebastian<br>
> --<br>
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted<br>
> by The Linux Foundation<br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.cs.uiuc.edu/pipermail/llvmdev/attachments/20130125/d6cf234a/attachment-0001.html" target="_blank">http://lists.cs.uiuc.edu/pipermail/llvmdev/attachments/20130125/d6cf234a/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Fri, 25 Jan 2013 15:03:48 -0800<br>
From: Nadav Rotem <<a href="mailto:nrotem@apple.com">nrotem@apple.com</a>><br>
To: Renato Golin <<a href="mailto:renato.golin@linaro.org">renato.golin@linaro.org</a>><br>
Cc: LLVM Dev <<a href="mailto:llvmdev@cs.uiuc.edu">llvmdev@cs.uiuc.edu</a>><br>
Subject: Re: [LLVMdev] TargetLowering vs. TargetTransform<br>
Message-ID: <<a href="mailto:4AF031DB-A805-4154-AD95-516B85A79F20@apple.com">4AF031DB-A805-4154-AD95-516B85A79F20@apple.com</a>><br>
Content-Type: text/plain; CHARSET=US-ASCII<br>
<br>
><br>
> TargetTransform (TT) only has the free checks on types, while TargetLowering (TL) has on SDValue and destination type.<br>
><br>
<br>
Yes. This is a limitation of the current API. The design decision behind it was that in many cases you want to know the cost of IR before you generate it.<br>
For example, during vectorization you want to know how a particular IR would look if you were to vectorize it. Also, we wanted to rely on tables as much as possible. We did not want to write code to resemble ISel in order to estimate the cost. Is this something that we can live with ?<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Fri, 25 Jan 2013 17:06:33 -0600<br>
From: Sebastian Pop <<a href="mailto:spop@codeaurora.org">spop@codeaurora.org</a>><br>
To: Daniel Dunbar <<a href="mailto:daniel@zuster.org">daniel@zuster.org</a>><br>
Cc: "<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a> Developers" <<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a>>, Daniel<br>
Dunbar <<a href="mailto:daniel_dunbar@apple.com">daniel_dunbar@apple.com</a>>, LLVM Developers Mailing List<br>
<<a href="mailto:llvmdev@cs.uiuc.edu">llvmdev@cs.uiuc.edu</a>><br>
Subject: Re: [LLVMdev] [cfe-dev] RFC: put commit messages in *-commits<br>
subject lines?<br>
Message-ID: <<a href="mailto:20130125230633.GA21987@codeaurora.org">20130125230633.GA21987@codeaurora.org</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
Daniel Dunbar wrote:<br>
> I'm a bit hesitant to just hack up the installed copy of svnmailer, are we<br>
> sure this patch hasn't been dealt with in an upstream version?<br>
<br>
I don't see that change in the last dev version:<br>
<a href="http://storage.perlig.de/svnmailer/svnmailer-1.1.0-dev-r1373.tar.bz2" target="_blank">http://storage.perlig.de/svnmailer/svnmailer-1.1.0-dev-r1373.tar.bz2</a><br>
<br>
> > -diff_command = /usr/bin/diff -u -L %(label_from)s -L %(label_to)s<br>
> > %(from)s %(to)s<br>
> > +diff_command = /usr/bin/diff -up -L %(label_from)s -L %(label_to)s<br>
> > %(from)s %(to)s<br>
> > generate_diffs = add copy modify propchange<br>
> ><br>
><br>
> I'll go ahead and make this change.<br>
<br>
Thanks,<br>
Sebastian<br>
--<br>
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Fri, 25 Jan 2013 15:11:40 -0800<br>
From: Daniel Dunbar <<a href="mailto:daniel@zuster.org">daniel@zuster.org</a>><br>
To: Sebastian Pop <<a href="mailto:spop@codeaurora.org">spop@codeaurora.org</a>><br>
Cc: "<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a> Developers" <<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a>>, Daniel<br>
Dunbar <<a href="mailto:daniel_dunbar@apple.com">daniel_dunbar@apple.com</a>>, LLVM Developers Mailing List<br>
<<a href="mailto:llvmdev@cs.uiuc.edu">llvmdev@cs.uiuc.edu</a>><br>
Subject: Re: [LLVMdev] [cfe-dev] RFC: put commit messages in *-commits<br>
subject lines?<br>
Message-ID:<br>
<CAEU8z6-wn8SjDtJiDoGxbyVR=<a href="mailto:6QCSQczT7Y8LvvGtbyw5hXFFw@mail.gmail.com">6QCSQczT7Y8LvvGtbyw5hXFFw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Yup, I didn't either. I went ahead and hacked up a copy with that change<br>
and am switching it over now.<br>
<br>
- Daniel<br>
<br>
<br>
On Fri, Jan 25, 2013 at 3:06 PM, Sebastian Pop <<a href="mailto:spop@codeaurora.org">spop@codeaurora.org</a>> wrote:<br>
<br>
> Daniel Dunbar wrote:<br>
> > I'm a bit hesitant to just hack up the installed copy of svnmailer, are<br>
> we<br>
> > sure this patch hasn't been dealt with in an upstream version?<br>
><br>
> I don't see that change in the last dev version:<br>
> <a href="http://storage.perlig.de/svnmailer/svnmailer-1.1.0-dev-r1373.tar.bz2" target="_blank">http://storage.perlig.de/svnmailer/svnmailer-1.1.0-dev-r1373.tar.bz2</a><br>
><br>
> > > -diff_command = /usr/bin/diff -u -L %(label_from)s -L %(label_to)s<br>
> > > %(from)s %(to)s<br>
> > > +diff_command = /usr/bin/diff -up -L %(label_from)s -L %(label_to)s<br>
> > > %(from)s %(to)s<br>
> > > generate_diffs = add copy modify propchange<br>
> > ><br>
> ><br>
> > I'll go ahead and make this change.<br>
><br>
> Thanks,<br>
> Sebastian<br>
> --<br>
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted<br>
> by The Linux Foundation<br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.cs.uiuc.edu/pipermail/llvmdev/attachments/20130125/a8245c63/attachment-0001.html" target="_blank">http://lists.cs.uiuc.edu/pipermail/llvmdev/attachments/20130125/a8245c63/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Fri, 25 Jan 2013 15:15:46 -0800<br>
From: Daniel Dunbar <<a href="mailto:daniel@zuster.org">daniel@zuster.org</a>><br>
To: Sebastian Pop <<a href="mailto:spop@codeaurora.org">spop@codeaurora.org</a>><br>
Cc: "<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a> Developers" <<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a>>, Daniel<br>
Dunbar <<a href="mailto:daniel_dunbar@apple.com">daniel_dunbar@apple.com</a>>, LLVM Developers Mailing List<br>
<<a href="mailto:llvmdev@cs.uiuc.edu">llvmdev@cs.uiuc.edu</a>><br>
Subject: Re: [LLVMdev] [cfe-dev] RFC: put commit messages in *-commits<br>
subject lines?<br>
Message-ID:<br>
<<a href="mailto:CAEU8z69qnQnZ44m%2BeTeMsvEGtReK288SFKUC4Tyk-wzgJeiOyQ@mail.gmail.com">CAEU8z69qnQnZ44m+eTeMsvEGtReK288SFKUC4Tyk-wzgJeiOyQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Ok, this is done and seems to work.<br>
<br>
As far as Chris's request for getting "key directory" paths into the commit<br>
message, I thought about working on it, but in the end I'm not sure why we<br>
shouldn't just encourage people to self-tag their leading commit line with<br>
some sort of standard key ([MC], [Target/Mips], whatever).<br>
<br>
- Daniel<br>
<br>
<br>
On Fri, Jan 25, 2013 at 3:11 PM, Daniel Dunbar <<a href="mailto:daniel@zuster.org">daniel@zuster.org</a>> wrote:<br>
<br>
> Yup, I didn't either. I went ahead and hacked up a copy with that change<br>
> and am switching it over now.<br>
><br>
> - Daniel<br>
><br>
><br>
> On Fri, Jan 25, 2013 at 3:06 PM, Sebastian Pop <<a href="mailto:spop@codeaurora.org">spop@codeaurora.org</a>>wrote:<br>
><br>
>> Daniel Dunbar wrote:<br>
>> > I'm a bit hesitant to just hack up the installed copy of svnmailer, are<br>
>> we<br>
>> > sure this patch hasn't been dealt with in an upstream version?<br>
>><br>
>> I don't see that change in the last dev version:<br>
>> <a href="http://storage.perlig.de/svnmailer/svnmailer-1.1.0-dev-r1373.tar.bz2" target="_blank">http://storage.perlig.de/svnmailer/svnmailer-1.1.0-dev-r1373.tar.bz2</a><br>
>><br>
>> > > -diff_command = /usr/bin/diff -u -L %(label_from)s -L %(label_to)s<br>
>> > > %(from)s %(to)s<br>
>> > > +diff_command = /usr/bin/diff -up -L %(label_from)s -L %(label_to)s<br>
>> > > %(from)s %(to)s<br>
>> > > generate_diffs = add copy modify propchange<br>
>> > ><br>
>> ><br>
>> > I'll go ahead and make this change.<br>
>><br>
>> Thanks,<br>
>> Sebastian<br>
>> --<br>
>> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted<br>
>> by The Linux Foundation<br>
>><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.cs.uiuc.edu/pipermail/llvmdev/attachments/20130125/4c2976f4/attachment-0001.html" target="_blank">http://lists.cs.uiuc.edu/pipermail/llvmdev/attachments/20130125/4c2976f4/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Sat, 26 Jan 2013 08:40:50 +0900<br>
From: NAKAMURA Takumi <<a href="mailto:geek4civic@gmail.com">geek4civic@gmail.com</a>><br>
To: Daniel Dunbar <<a href="mailto:daniel@zuster.org">daniel@zuster.org</a>><br>
Cc: Chris Lattner <<a href="mailto:sabre@nondot.org">sabre@nondot.org</a>>, Sebastian Pop<br>
<<a href="mailto:spop@codeaurora.org">spop@codeaurora.org</a>>, "<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a> Developers"<br>
<<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a>>, Daniel Dunbar <<a href="mailto:daniel_dunbar@apple.com">daniel_dunbar@apple.com</a>>, LLVM<br>
Developers Mailing List <<a href="mailto:llvmdev@cs.uiuc.edu">llvmdev@cs.uiuc.edu</a>><br>
Subject: Re: [LLVMdev] [cfe-dev] RFC: put commit messages in *-commits<br>
subject lines?<br>
Message-ID:<br>
<<a href="mailto:CADiQthOGj%2Bv42gGovfjES5Y_bSy-VGp_bkzhqw2pgnLgYiSJoQ@mail.gmail.com">CADiQthOGj+v42gGovfjES5Y_bSy-VGp_bkzhqw2pgnLgYiSJoQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
2013/1/26 Daniel Dunbar <<a href="mailto:daniel@zuster.org">daniel@zuster.org</a>>:<br>
> Ok, this is done and seems to work.<br>
<br>
Cool!<br>
<br>
> As far as Chris's request for getting "key directory" paths into the commit<br>
> message, I thought about working on it, but in the end I'm not sure why we<br>
> shouldn't just encourage people to self-tag their leading commit line with<br>
> some sort of standard key ([MC], [Target/Mips], whatever).<br>
<br>
+1. At least for now, I think it might be redundant to add "key directories".<br>
We may watch on how better this change would have been.<br>
<br>
...Takumi<br>
<br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Sat, 26 Jan 2013 01:00:13 +0100<br>
From: Tobias Grosser <<a href="mailto:tobias@grosser.es">tobias@grosser.es</a>><br>
To: Daniel Dunbar <<a href="mailto:daniel@zuster.org">daniel@zuster.org</a>><br>
Cc: Sebastian Pop <<a href="mailto:spop@codeaurora.org">spop@codeaurora.org</a>>, "<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a><br>
Developers" <<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a>>, Daniel Dunbar<br>
<<a href="mailto:daniel_dunbar@apple.com">daniel_dunbar@apple.com</a>>, LLVM Developers Mailing List<br>
<<a href="mailto:llvmdev@cs.uiuc.edu">llvmdev@cs.uiuc.edu</a>><br>
Subject: Re: [LLVMdev] [cfe-dev] RFC: put commit messages in *-commits<br>
subject lines?<br>
Message-ID: <<a href="mailto:51031C8D.6090005@grosser.es">51031C8D.6090005@grosser.es</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
On 01/26/2013 12:15 AM, Daniel Dunbar wrote:<br>
> Ok, this is done and seems to work.<br>
><br>
> As far as Chris's request for getting "key directory" paths into the<br>
> commit message, I thought about working on it, but in the end I'm not<br>
> sure why we shouldn't just encourage people to self-tag their leading<br>
> commit line with some sort of standard key ([MC], [Target/Mips], whatever).<br>
<br>
Very nice.<br>
<br>
While at that, who can get rid of the [llvm],[cfe-commits], ...<br>
prefixes? I remember we agreed they just cost screen real estate.<br>
<br>
Tobi<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 8<br>
Date: Fri, 25 Jan 2013 16:07:42 -0800<br>
From: Daniel Dunbar <<a href="mailto:daniel@zuster.org">daniel@zuster.org</a>><br>
To: Tanya Lattner <<a href="mailto:tonic@nondot.org">tonic@nondot.org</a>>, Chris Lattner<br>
<<a href="mailto:sabre@nondot.org">sabre@nondot.org</a>>, John Criswell <<a href="mailto:criswell@illinois.edu">criswell@illinois.edu</a>><br>
Cc: Sebastian Pop <<a href="mailto:spop@codeaurora.org">spop@codeaurora.org</a>>, "<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a><br>
Developers" <<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a>>, Daniel Dunbar<br>
<<a href="mailto:daniel_dunbar@apple.com">daniel_dunbar@apple.com</a>>, LLVM Developers Mailing List<br>
<<a href="mailto:llvmdev@cs.uiuc.edu">llvmdev@cs.uiuc.edu</a>><br>
Subject: Re: [LLVMdev] [cfe-dev] RFC: put commit messages in *-commits<br>
subject lines?<br>
Message-ID:<br>
<CAEU8z680rOiCMAEt_Z+QTxwCcxsk5Fm8=<a href="mailto:10%2B_C0s2pOQhuXzWg@mail.gmail.com">10+_C0s2pOQhuXzWg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
On Fri, Jan 25, 2013 at 4:00 PM, Tobias Grosser <<a href="mailto:tobias@grosser.es">tobias@grosser.es</a>> wrote:<br>
<br>
> On 01/26/2013 12:15 AM, Daniel Dunbar wrote:<br>
><br>
>> Ok, this is done and seems to work.<br>
>><br>
>> As far as Chris's request for getting "key directory" paths into the<br>
>> commit message, I thought about working on it, but in the end I'm not<br>
>> sure why we shouldn't just encourage people to self-tag their leading<br>
>> commit line with some sort of standard key ([MC], [Target/Mips],<br>
>> whatever).<br>
>><br>
><br>
> Very nice.<br>
><br>
> While at that, who can get rid of the [llvm],[cfe-commits], ... prefixes?<br>
> I remember we agreed they just cost screen real estate.<br>
><br>
<br>
That needs to be done by someone with admin access to the mailing lists,<br>
Chris, Tanya, John C., not sure who else?<br>
<br>
- Daniel<br>
<br>
<br>
><br>
> Tobi<br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.cs.uiuc.edu/pipermail/llvmdev/attachments/20130125/8c4039fe/attachment-0001.html" target="_blank">http://lists.cs.uiuc.edu/pipermail/llvmdev/attachments/20130125/8c4039fe/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 9<br>
Date: Fri, 25 Jan 2013 16:28:29 -0800<br>
From: Eli Bendersky <<a href="mailto:eliben@google.com">eliben@google.com</a>><br>
To: Daniel Dunbar <<a href="mailto:daniel@zuster.org">daniel@zuster.org</a>><br>
Cc: Daniel Dunbar <<a href="mailto:daniel_dunbar@apple.com">daniel_dunbar@apple.com</a>>, Sebastian Pop<br>
<<a href="mailto:spop@codeaurora.org">spop@codeaurora.org</a>>, Chris Lattner <<a href="mailto:sabre@nondot.org">sabre@nondot.org</a>>, LLVM<br>
Developers Mailing List <<a href="mailto:llvmdev@cs.uiuc.edu">llvmdev@cs.uiuc.edu</a>>, Tanya Lattner<br>
<<a href="mailto:tonic@nondot.org">tonic@nondot.org</a>>, "<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a> Developers"<br>
<<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a>><br>
Subject: Re: [LLVMdev] [cfe-dev] RFC: put commit messages in *-commits<br>
subject lines?<br>
Message-ID:<br>
<<a href="mailto:CACLQwhFTtZa4_KRX0eFwDM6TVmZoLbfQYWBfuBiqAe8irQQZOw@mail.gmail.com">CACLQwhFTtZa4_KRX0eFwDM6TVmZoLbfQYWBfuBiqAe8irQQZOw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
On Fri, Jan 25, 2013 at 4:07 PM, Daniel Dunbar <<a href="mailto:daniel@zuster.org">daniel@zuster.org</a>> wrote:<br>
><br>
><br>
><br>
> On Fri, Jan 25, 2013 at 4:00 PM, Tobias Grosser <<a href="mailto:tobias@grosser.es">tobias@grosser.es</a>> wrote:<br>
>><br>
>> On 01/26/2013 12:15 AM, Daniel Dunbar wrote:<br>
>>><br>
>>> Ok, this is done and seems to work.<br>
>>><br>
>>> As far as Chris's request for getting "key directory" paths into the<br>
>>> commit message, I thought about working on it, but in the end I'm not<br>
>>> sure why we shouldn't just encourage people to self-tag their leading<br>
>>> commit line with some sort of standard key ([MC], [Target/Mips],<br>
>>> whatever).<br>
>><br>
>><br>
>> Very nice.<br>
>><br>
>> While at that, who can get rid of the [llvm],[cfe-commits], ... prefixes?<br>
>> I remember we agreed they just cost screen real estate.<br>
><br>
<br>
Careful here, these may be used to set up filters in mail clients, and<br>
an alternative has to be provided.<br>
<br>
For instance, I have a filter that sends all [compiler-rt] related<br>
mail to its own folder, which is quite important for me.<br>
<br>
Eli<br>
<br>
<br>
------------------------------<br>
<br>
Message: 10<br>
Date: Fri, 25 Jan 2013 16:37:37 -0800<br>
From: David Blaikie <<a href="mailto:dblaikie@gmail.com">dblaikie@gmail.com</a>><br>
To: Eli Bendersky <<a href="mailto:eliben@google.com">eliben@google.com</a>><br>
Cc: Daniel Dunbar <<a href="mailto:daniel_dunbar@apple.com">daniel_dunbar@apple.com</a>>, Sebastian Pop<br>
<<a href="mailto:spop@codeaurora.org">spop@codeaurora.org</a>>, Chris Lattner <<a href="mailto:sabre@nondot.org">sabre@nondot.org</a>>, Tanya Lattner<br>
<<a href="mailto:tonic@nondot.org">tonic@nondot.org</a>>, "<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a> Developers"<br>
<<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a>>, LLVM Developers Mailing List<br>
<<a href="mailto:llvmdev@cs.uiuc.edu">llvmdev@cs.uiuc.edu</a>><br>
Subject: Re: [LLVMdev] [cfe-dev] RFC: put commit messages in *-commits<br>
subject lines?<br>
Message-ID:<br>
<<a href="mailto:CAENS6EtGL6o3wUV2zcUkge_vzX2zgahOsQWDLKJ5HWFuLJG5vw@mail.gmail.com">CAENS6EtGL6o3wUV2zcUkge_vzX2zgahOsQWDLKJ5HWFuLJG5vw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
On Fri, Jan 25, 2013 at 4:28 PM, Eli Bendersky <<a href="mailto:eliben@google.com">eliben@google.com</a>> wrote:<br>
> On Fri, Jan 25, 2013 at 4:07 PM, Daniel Dunbar <<a href="mailto:daniel@zuster.org">daniel@zuster.org</a>> wrote:<br>
>><br>
>><br>
>><br>
>> On Fri, Jan 25, 2013 at 4:00 PM, Tobias Grosser <<a href="mailto:tobias@grosser.es">tobias@grosser.es</a>> wrote:<br>
>>><br>
>>> On 01/26/2013 12:15 AM, Daniel Dunbar wrote:<br>
>>>><br>
>>>> Ok, this is done and seems to work.<br>
>>>><br>
>>>> As far as Chris's request for getting "key directory" paths into the<br>
>>>> commit message, I thought about working on it, but in the end I'm not<br>
>>>> sure why we shouldn't just encourage people to self-tag their leading<br>
>>>> commit line with some sort of standard key ([MC], [Target/Mips],<br>
>>>> whatever).<br>
>>><br>
>>><br>
>>> Very nice.<br>
>>><br>
>>> While at that, who can get rid of the [llvm],[cfe-commits], ... prefixes?<br>
>>> I remember we agreed they just cost screen real estate.<br>
>><br>
><br>
> Careful here, these may be used to set up filters in mail clients, and<br>
> an alternative has to be provided.<br>
<br>
Agreed.<br>
<br>
> For instance, I have a filter that sends all [compiler-rt] related<br>
> mail to its own folder, which is quite important for me.<br>
<br>
the [compiler-rt] prefix is for the specific repository, rather than<br>
the mailing list - that would remain (it's part of the svn mail<br>
sending process), but the mailing list prefix is a property of the<br>
mailing list software overall, which is what's going to (potentially)<br>
be removed.<br>
<br>
That being said, even though I (& probably most gmail users) have<br>
mailing list rules setup based on list headers rather than subject<br>
prefixes, like you, I wouldn't be sure that everyone has this setup or<br>
that it's convenient for everyone to do so.<br>
<br>
I'd like this change, I'm just not sure how to evaluate whether it's<br>
correct (short of changing it seeing how many people complain/how many<br>
of them cannot be helped/fixed)<br>
<br>
<br>
------------------------------<br>
<br>
Message: 11<br>
Date: Fri, 25 Jan 2013 16:41:53 -0800<br>
From: Eli Bendersky <<a href="mailto:eliben@google.com">eliben@google.com</a>><br>
To: David Blaikie <<a href="mailto:dblaikie@gmail.com">dblaikie@gmail.com</a>><br>
Cc: Daniel Dunbar <<a href="mailto:daniel_dunbar@apple.com">daniel_dunbar@apple.com</a>>, Sebastian Pop<br>
<<a href="mailto:spop@codeaurora.org">spop@codeaurora.org</a>>, Chris Lattner <<a href="mailto:sabre@nondot.org">sabre@nondot.org</a>>, Tanya Lattner<br>
<<a href="mailto:tonic@nondot.org">tonic@nondot.org</a>>, "<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a> Developers"<br>
<<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a>>, LLVM Developers Mailing List<br>
<<a href="mailto:llvmdev@cs.uiuc.edu">llvmdev@cs.uiuc.edu</a>><br>
Subject: Re: [LLVMdev] [cfe-dev] RFC: put commit messages in *-commits<br>
subject lines?<br>
Message-ID:<br>
<CACLQwhFmq=QJuRSyPxWE6e=eCTmRL4tWhYyz=<a href="mailto:3aYXbdCoYsHkg@mail.gmail.com">3aYXbdCoYsHkg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
On Fri, Jan 25, 2013 at 4:37 PM, David Blaikie <<a href="mailto:dblaikie@gmail.com">dblaikie@gmail.com</a>> wrote:<br>
> On Fri, Jan 25, 2013 at 4:28 PM, Eli Bendersky <<a href="mailto:eliben@google.com">eliben@google.com</a>> wrote:<br>
>> On Fri, Jan 25, 2013 at 4:07 PM, Daniel Dunbar <<a href="mailto:daniel@zuster.org">daniel@zuster.org</a>> wrote:<br>
>>><br>
>>><br>
>>><br>
>>> On Fri, Jan 25, 2013 at 4:00 PM, Tobias Grosser <<a href="mailto:tobias@grosser.es">tobias@grosser.es</a>> wrote:<br>
>>>><br>
>>>> On 01/26/2013 12:15 AM, Daniel Dunbar wrote:<br>
>>>>><br>
>>>>> Ok, this is done and seems to work.<br>
>>>>><br>
>>>>> As far as Chris's request for getting "key directory" paths into the<br>
>>>>> commit message, I thought about working on it, but in the end I'm not<br>
>>>>> sure why we shouldn't just encourage people to self-tag their leading<br>
>>>>> commit line with some sort of standard key ([MC], [Target/Mips],<br>
>>>>> whatever).<br>
>>>><br>
>>>><br>
>>>> Very nice.<br>
>>>><br>
>>>> While at that, who can get rid of the [llvm],[cfe-commits], ... prefixes?<br>
>>>> I remember we agreed they just cost screen real estate.<br>
>>><br>
>><br>
>> Careful here, these may be used to set up filters in mail clients, and<br>
>> an alternative has to be provided.<br>
><br>
> Agreed.<br>
><br>
>> For instance, I have a filter that sends all [compiler-rt] related<br>
>> mail to its own folder, which is quite important for me.<br>
><br>
> the [compiler-rt] prefix is for the specific repository, rather than<br>
> the mailing list - that would remain (it's part of the svn mail<br>
> sending process), but the mailing list prefix is a property of the<br>
> mailing list software overall, which is what's going to (potentially)<br>
> be removed.<br>
><br>
<br>
OK, I see.<br>
<br>
> That being said, even though I (& probably most gmail users) have<br>
> mailing list rules setup based on list headers rather than subject<br>
> prefixes, like you, I wouldn't be sure that everyone has this setup or<br>
> that it's convenient for everyone to do so.<br>
><br>
> I'd like this change, I'm just not sure how to evaluate whether it's<br>
> correct (short of changing it seeing how many people complain/how many<br>
> of them cannot be helped/fixed)<br>
<br>
I guess that the need can be summarized to:<br>
<br>
- If email comes from separate email addresses (or "to" separate<br>
addresses), further specification in the subject is superfluous and<br>
can be nuked.<br>
- If email is otherwise indistinguishable but comes from different<br>
sub-projects, some specification in the subject has to be retained to<br>
allow effective mailbox management.<br>
<br>
What am I missing?<br>
<br>
Eli<br>
<br>
<br>
------------------------------<br>
<br>
Message: 12<br>
Date: Sat, 26 Jan 2013 13:16:57 +0000<br>
From: Renato Golin <<a href="mailto:renato.golin@linaro.org">renato.golin@linaro.org</a>><br>
To: Nadav Rotem <<a href="mailto:nrotem@apple.com">nrotem@apple.com</a>><br>
Cc: LLVM Dev <<a href="mailto:llvmdev@cs.uiuc.edu">llvmdev@cs.uiuc.edu</a>><br>
Subject: Re: [LLVMdev] TargetLowering vs. TargetTransform<br>
Message-ID:<br>
<CAMSE1kf=<a href="mailto:FD8rRu9gj3FNe1esiuXWjdiZf5AXSYovfTWuGUgGSA@mail.gmail.com">FD8rRu9gj3FNe1esiuXWjdiZf5AXSYovfTWuGUgGSA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
On 25 January 2013 23:03, Nadav Rotem <<a href="mailto:nrotem@apple.com">nrotem@apple.com</a>> wrote:<br>
<br>
> Yes. This is a limitation of the current API. The design decision behind<br>
> it was that in many cases you want to know the cost of IR before you<br>
> generate it.<br>
><br>
<br>
That makes sense.<br>
<br>
<br>
Also, we wanted to rely on tables as much as possible. We did not want to<br>
> write code to resemble ISel in order to estimate the cost. Is this<br>
> something that we can live with ?<br>
><br>
<br>
It depends on the final design intentions. If these costs are only ever<br>
going to be used by the vectorization, or if other optimizations are going<br>
to start using TargetTransformInfo for cost information, than yes, it makes<br>
sense to begin focusing cost models on TTI. But if other passes call TL<br>
directly, then we might re-think the strategy.<br>
<br>
It looks to me that only lowering would need to call TL's costs, since they<br>
can be different than a more high level cost, and possibly assume that the<br>
code is already valid and checked, which is not the case for most<br>
transformations, including the vectorization. I think this is more or less<br>
what you were saying before.<br>
<br>
I'll give it a few tries and send to the list so we can discuss with more<br>
concrete implementations.<br>
<br>
cheers,<br>
--renato<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.cs.uiuc.edu/pipermail/llvmdev/attachments/20130126/db160fb4/attachment-0001.html" target="_blank">http://lists.cs.uiuc.edu/pipermail/llvmdev/attachments/20130126/db160fb4/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 13<br>
Date: Sat, 26 Jan 2013 15:22:45 +0100<br>
From: Tobias Grosser <<a href="mailto:tobias@grosser.es">tobias@grosser.es</a>><br>
To: Eli Bendersky <<a href="mailto:eliben@google.com">eliben@google.com</a>><br>
Cc: Daniel Dunbar <<a href="mailto:daniel_dunbar@apple.com">daniel_dunbar@apple.com</a>>, Sebastian Pop<br>
<<a href="mailto:spop@codeaurora.org">spop@codeaurora.org</a>>, Chris Lattner <<a href="mailto:sabre@nondot.org">sabre@nondot.org</a>>, Tanya Lattner<br>
<<a href="mailto:tonic@nondot.org">tonic@nondot.org</a>>, LLVM Developers Mailing List<br>
<<a href="mailto:llvmdev@cs.uiuc.edu">llvmdev@cs.uiuc.edu</a>>, "<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a> Developers"<br>
<<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a>><br>
Subject: Re: [LLVMdev] [cfe-dev] RFC: put commit messages in *-commits<br>
subject lines?<br>
Message-ID: <<a href="mailto:5103E6B5.2060807@grosser.es">5103E6B5.2060807@grosser.es</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
On 01/26/2013 01:41 AM, Eli Bendersky wrote:<br>
> On Fri, Jan 25, 2013 at 4:37 PM, David Blaikie <<a href="mailto:dblaikie@gmail.com">dblaikie@gmail.com</a>> wrote:<br>
>> On Fri, Jan 25, 2013 at 4:28 PM, Eli Bendersky <<a href="mailto:eliben@google.com">eliben@google.com</a>> wrote:<br>
>>> On Fri, Jan 25, 2013 at 4:07 PM, Daniel Dunbar <<a href="mailto:daniel@zuster.org">daniel@zuster.org</a>> wrote:<br>
>>>><br>
>>>><br>
>>>><br>
>>>> On Fri, Jan 25, 2013 at 4:00 PM, Tobias Grosser <<a href="mailto:tobias@grosser.es">tobias@grosser.es</a>> wrote:<br>
>>>>><br>
>>>>> On 01/26/2013 12:15 AM, Daniel Dunbar wrote:<br>
>>>>>><br>
>>>>>> Ok, this is done and seems to work.<br>
>>>>>><br>
>>>>>> As far as Chris's request for getting "key directory" paths into the<br>
>>>>>> commit message, I thought about working on it, but in the end I'm not<br>
>>>>>> sure why we shouldn't just encourage people to self-tag their leading<br>
>>>>>> commit line with some sort of standard key ([MC], [Target/Mips],<br>
>>>>>> whatever).<br>
>>>>><br>
>>>>><br>
>>>>> Very nice.<br>
>>>>><br>
>>>>> While at that, who can get rid of the [llvm],[cfe-commits], ... prefixes?<br>
>>>>> I remember we agreed they just cost screen real estate.<br>
>>>><br>
>>><br>
>>> Careful here, these may be used to set up filters in mail clients, and<br>
>>> an alternative has to be provided.<br>
>><br>
>> Agreed.<br>
>><br>
>>> For instance, I have a filter that sends all [compiler-rt] related<br>
>>> mail to its own folder, which is quite important for me.<br>
>><br>
>> the [compiler-rt] prefix is for the specific repository, rather than<br>
>> the mailing list - that would remain (it's part of the svn mail<br>
>> sending process), but the mailing list prefix is a property of the<br>
>> mailing list software overall, which is what's going to (potentially)<br>
>> be removed.<br>
>><br>
><br>
> OK, I see.<br>
><br>
>> That being said, even though I (& probably most gmail users) have<br>
>> mailing list rules setup based on list headers rather than subject<br>
>> prefixes, like you, I wouldn't be sure that everyone has this setup or<br>
>> that it's convenient for everyone to do so.<br>
>><br>
>> I'd like this change, I'm just not sure how to evaluate whether it's<br>
>> correct (short of changing it seeing how many people complain/how many<br>
>> of them cannot be helped/fixed)<br>
><br>
> I guess that the need can be summarized to:<br>
><br>
> - If email comes from separate email addresses (or "to" separate<br>
> addresses), further specification in the subject is superfluous and<br>
> can be nuked.<br>
> - If email is otherwise indistinguishable but comes from different<br>
> sub-projects, some specification in the subject has to be retained to<br>
> allow effective mailbox management.<br>
><br>
> What am I missing?<br>
<br>
I don't see anything missing.<br>
<br>
I asked to remove the list name from the subject, as it is already<br>
provided in the "List-Id" header of all mailing list emails and is<br>
consequently redundant. The different svn sub-projects are useful and I<br>
don't think we should remove this information.<br>
<br>
Chris replied to that request earlier (15. Nov):<br>
<br>
> I agree that the list name is redundant and should be dropped, but<br>
> the revision number is compact and very useful...<br>
><br>
> -Chris<br>
<br>
If we agreed to perform this change and we found the person who can<br>
change it, we can probably give a heads-up a couple of days before to<br>
see if anybody will have major issues.<br>
<br>
Cheers,<br>
Tobi<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 14<br>
Date: Sat, 26 Jan 2013 17:47:03 +0100<br>
From: Duncan Sands <<a href="mailto:baldrick@free.fr">baldrick@free.fr</a>><br>
To: <a href="mailto:llvmdev@cs.uiuc.edu">llvmdev@cs.uiuc.edu</a><br>
Subject: Re: [LLVMdev] Testing canaries<br>
Message-ID: <<a href="mailto:51040887.90309@free.fr">51040887.90309@free.fr</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
Hi Izabela,<br>
<br>
On 21/01/13 18:37, Izabela Maffra wrote:<br>
> Dear LLVMers,<br>
><br>
> I am trying to measure the performance overhead (if any) of the canaries<br>
> that clang inserts in the code. I would like to do this automatically, using the<br>
> LLVM test infra-structure. However, I am not sure if that is possible. Could<br>
> someone tell me which flags in the TEST.nightly.Makefile script, (or any other<br>
> script) I must change to have this done? Usually I insert canaries with the<br>
> following command line:<br>
><br>
> $> clang -S -fstack-protector hello.c<br>
><br>
> But I would like to know which part of LLVM calls the pass that inserts the<br>
> canaries. It seems it is llc, as the pass that inserts the canaries is in<br>
> /lib/CodeGen/StackProtector.cpp. Yet, I cannot see 'fstack-protector' in the llc<br>
> --help list, although I can see 'stack-protector-buffer-size' in llc --help.<br>
<br>
the -fstack-protector option is processed by the clang front-end. If you grep<br>
for stack-protector in the clang source, you will discover that the action is<br>
happening in clang/lib/Driver/Tools.cpp, here:<br>
<br>
if (StackProtectorLevel) {<br>
CmdArgs.push_back("-stack-protector");<br>
CmdArgs.push_back(Args.MakeArgString(Twine(StackProtectorLevel)));<br>
}<br>
<br>
The argument -stack-protector is for the code generators, and you should find<br>
that llc has the same argument. However if you look for it it doesn't seem to<br>
exist:<br>
<br>
$ llc -help | grep stack-protector<br>
-stack-protector-buffer-size=<uint> - Lower bound for a buffer to be<br>
considered for stack protection<br>
<br>
What is going on? Some options aren't considered generally useful and are<br>
hidden. If you use -help-hidden you get to see all options:<br>
<br>
$ llc -help-hidden | grep stack-protector<br>
=stack-protector - Insert stack protectors<br>
=stack-protector - Insert stack protectors<br>
-stack-protector-buffer-size=<uint> - Lower bound for a buffer to be<br>
considered for stack protection<br>
<br>
There it is! It's not clear to me why -stack-protector is hidden away like<br>
that. Hidden options work just the same as visible options: just pass<br>
-stack-protector to llc.<br>
<br>
Ciao, Duncan.<br>
<br>
<br>
------------------------------<br>
<br>
Message: 15<br>
Date: Sat, 26 Jan 2013 09:49:35 -0800<br>
From: David Blaikie <<a href="mailto:dblaikie@gmail.com">dblaikie@gmail.com</a>><br>
To: Tobias Grosser <<a href="mailto:tobias@grosser.es">tobias@grosser.es</a>><br>
Cc: Daniel Dunbar <<a href="mailto:daniel_dunbar@apple.com">daniel_dunbar@apple.com</a>>, Sebastian Pop<br>
<<a href="mailto:spop@codeaurora.org">spop@codeaurora.org</a>>, Chris Lattner <<a href="mailto:sabre@nondot.org">sabre@nondot.org</a>>, Tanya Lattner<br>
<<a href="mailto:tonic@nondot.org">tonic@nondot.org</a>>, LLVM Developers Mailing List<br>
<<a href="mailto:llvmdev@cs.uiuc.edu">llvmdev@cs.uiuc.edu</a>>, "<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a> Developers"<br>
<<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a>><br>
Subject: Re: [LLVMdev] [cfe-dev] RFC: put commit messages in *-commits<br>
subject lines?<br>
Message-ID:<br>
<CAENS6Ev1g=qzp=+<a href="mailto:Vk4JJuiwiBUB8vTL_yd7M6eHzWJc76Rfe9g@mail.gmail.com">Vk4JJuiwiBUB8vTL_yd7M6eHzWJc76Rfe9g@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
On Sat, Jan 26, 2013 at 6:22 AM, Tobias Grosser <<a href="mailto:tobias@grosser.es">tobias@grosser.es</a>> wrote:<br>
> On 01/26/2013 01:41 AM, Eli Bendersky wrote:<br>
>><br>
>> On Fri, Jan 25, 2013 at 4:37 PM, David Blaikie <<a href="mailto:dblaikie@gmail.com">dblaikie@gmail.com</a>> wrote:<br>
>>><br>
>>> On Fri, Jan 25, 2013 at 4:28 PM, Eli Bendersky <<a href="mailto:eliben@google.com">eliben@google.com</a>> wrote:<br>
>>>><br>
>>>> On Fri, Jan 25, 2013 at 4:07 PM, Daniel Dunbar <<a href="mailto:daniel@zuster.org">daniel@zuster.org</a>><br>
>>>> wrote:<br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>> On Fri, Jan 25, 2013 at 4:00 PM, Tobias Grosser <<a href="mailto:tobias@grosser.es">tobias@grosser.es</a>><br>
>>>>> wrote:<br>
>>>>>><br>
>>>>>><br>
>>>>>> On 01/26/2013 12:15 AM, Daniel Dunbar wrote:<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> Ok, this is done and seems to work.<br>
>>>>>>><br>
>>>>>>> As far as Chris's request for getting "key directory" paths into the<br>
>>>>>>> commit message, I thought about working on it, but in the end I'm not<br>
>>>>>>> sure why we shouldn't just encourage people to self-tag their leading<br>
>>>>>>> commit line with some sort of standard key ([MC], [Target/Mips],<br>
>>>>>>> whatever).<br>
>>>>>><br>
>>>>>><br>
>>>>>><br>
>>>>>> Very nice.<br>
>>>>>><br>
>>>>>> While at that, who can get rid of the [llvm],[cfe-commits], ...<br>
>>>>>> prefixes?<br>
>>>>>> I remember we agreed they just cost screen real estate.<br>
>>>>><br>
>>>>><br>
>>>><br>
>>>> Careful here, these may be used to set up filters in mail clients, and<br>
>>>> an alternative has to be provided.<br>
>>><br>
>>><br>
>>> Agreed.<br>
>>><br>
>>>> For instance, I have a filter that sends all [compiler-rt] related<br>
>>>> mail to its own folder, which is quite important for me.<br>
>>><br>
>>><br>
>>> the [compiler-rt] prefix is for the specific repository, rather than<br>
>>> the mailing list - that would remain (it's part of the svn mail<br>
>>> sending process), but the mailing list prefix is a property of the<br>
>>> mailing list software overall, which is what's going to (potentially)<br>
>>> be removed.<br>
>>><br>
>><br>
>> OK, I see.<br>
>><br>
>>> That being said, even though I (& probably most gmail users) have<br>
>>> mailing list rules setup based on list headers rather than subject<br>
>>> prefixes, like you, I wouldn't be sure that everyone has this setup or<br>
>>> that it's convenient for everyone to do so.<br>
>>><br>
>>> I'd like this change, I'm just not sure how to evaluate whether it's<br>
>>> correct (short of changing it seeing how many people complain/how many<br>
>>> of them cannot be helped/fixed)<br>
>><br>
>><br>
>> I guess that the need can be summarized to:<br>
>><br>
>> - If email comes from separate email addresses (or "to" separate<br>
>> addresses), further specification in the subject is superfluous and<br>
>> can be nuked.<br>
>> - If email is otherwise indistinguishable but comes from different<br>
>> sub-projects, some specification in the subject has to be retained to<br>
>> allow effective mailbox management.<br>
>><br>
>> What am I missing?<br>
><br>
><br>
> I don't see anything missing.<br>
><br>
> I asked to remove the list name from the subject, as it is already provided<br>
> in the "List-Id" header of all mailing list emails and is consequently<br>
> redundant. The different svn sub-projects are useful and I don't think we<br>
> should remove this information.<br>
><br>
> Chris replied to that request earlier (15. Nov):<br>
><br>
><br>
>> I agree that the list name is redundant and should be dropped, but<br>
>> the revision number is compact and very useful...<br>
>><br>
>> -Chris<br>
><br>
> If we agreed to perform this change and we found the person who can change<br>
> it, we can probably give a heads-up a couple of days before to see if<br>
> anybody will have major issues.<br>
<br>
SGTM - thanks for the recap/quotation. (but, yes, I'm not the person<br>
who can change that - hopefully Tanya or one of the other admins will<br>
speak up with details)<br>
<br>
<br>
------------------------------<br>
<br>
Message: 16<br>
Date: Sat, 26 Jan 2013 18:55:37 +0100<br>
From: "sara.elshobaky" <<a href="mailto:sara.elshobaky@laposte.net">sara.elshobaky@laposte.net</a>><br>
To: <a href="mailto:LLVMdev@cs.uiuc.edu">LLVMdev@cs.uiuc.edu</a><br>
Cc: <a href="mailto:sara.elshobaky@gmail.com">sara.elshobaky@gmail.com</a><br>
Subject: [LLVMdev] lli problem with a simple OpenGL<br>
Message-ID: <1500165980.71560.1359222937641.JavaMail.www@wwinf8316><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
?Hello,<br>
<br>
I wrote a very simple openGL application, as below<br>
<br>
#include<br>
#include<br>
int main(int argc, char **argv)<br>
{<br>
? glutInit(&argc, argv);<br>
? glutInitDisplayMode(GLUT_DOUBLE | GLUT_RGB | GLUT_DEPTH);<br>
? glutCreateWindow("red 3D lighted cube");<br>
? printf("GL_VERSION = %s\n",glGetString(GL_VERSION) );<br>
? return 0;<br>
}<br>
<br>
Compiling it with Clang and adding -lglut option worked correctly<br>
$ clang? simple.c? -o? simple? -lglut<br>
$ ./simple<br>
GL_VERSION = 2.1 Mesa 7.10.2<br>
<br>
But, adding the -emit-llvm option to clang, does not work as below<br>
$ clang -O3 -emit-llvm simple.c? -o simple.bc -lglut<br>
/usr/bin/ld: /usr/local/bin/../lib/LLVMgold.so: error loading plugin<br>
/usr/bin/ld: /usr/local/bin/../lib/LLVMgold.so: error in plugin cleanup (ignored)<br>
clang: error: linker command failed with exit code 1 (use -v to see invocation)<br>
<br>
Also, removing the -lglut option worked with clang but failed with lli as below<br>
$ clang -O3 -emit-llvm simple.c -c -o simple.bc<br>
$ lli simple.bc<br>
LLVM ERROR: Program used external function 'glutInit' which could not be resolved!<br>
<br>
Please advice how to run it using the llvm jit 'lli'<br>
<br>
Thanks in advance<br>
Sara<br>
<br>
<br>
<br>
Une messagerie gratuite, garantie ? vie et des services en plus, ?a vous tente ?<br>
Je cr?e ma bo?te mail <a href="http://www.laposte.net" target="_blank">www.laposte.net</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.cs.uiuc.edu/pipermail/llvmdev/attachments/20130126/71730723/attachment.html" target="_blank">http://lists.cs.uiuc.edu/pipermail/llvmdev/attachments/20130126/71730723/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
LLVMdev mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu">LLVMdev@cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br>
<br>
<br>
End of LLVMdev Digest, Vol 103, Issue 72<br>
****************************************<br>
</blockquote></div><br><br clear="all"><br>-- <br>Izabela Maffra.<br><br><i>Ciência da Computação<span></span><br>Universidade Federal de Minas Gerais<br>(31) 8615-3077</i><br><br>“Don't count the days, make the days count.”
― Muhammad Ali<br>
</div></div></div></div>