search for: 20180203

...ame if you ever do revise the ABI. > Maybe I don't understand, but I'm surprised that there is a significant burden to having aliases for now instead? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180203/26baaa32/attachment.html>

...names to the function that's exported. I'm not sure how we'd hack up the unresolved symbols in the module objects to match the exported symbol names. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180203/0f539d8c/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5213 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180203/0f539d8c/attachment.bin>

...ally by-design so that if we (or you) need to split apart the implementation, there are distinct names available. Until then, aliases seem very cheap to maintain? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180203/223d1983/attachment.html>

...erve the right to use a different name if you ever do revise the ABI. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5213 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180203/e847d501/attachment.bin>

...ps://lkml.org/lkml/2018/2/2/975 would be a bit of an understatement... -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5213 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180203/1cfad99e/attachment.bin>

...rnal-thunk'. The second flag implies the first. (Or should, if not, its a bug.) Our goal was that you needed exactly one flag to enable this in whatever form. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180203/f0d1405f/attachment-0001.html>

...lly since all of this needs to be backported to old versions of Clang and LLVM, we can't fix that and instead need to work around the existing infrastructure. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180203/0dc67d2e/attachment.html>

Hi all, I saw the retpoline mitigation landed in r323155. Are we ready to merge this to 6.0, or are there any open issues that we're waiting for? Also, were there any followups I should know about? Also, release notes please :-) Thanks, Hans -------------- next part -------------- An HTML attachment was scrubbed... URL:

...work. If you see anything that makes you think it isn't working, please give a shout (or file a bug) and we'll fix. > > Thanks, > Guenter > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180203/f3ba9d0a/attachment.html>

...at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > > -- Wei-Ren Chen (陳韋任) Homepage: https://people.cs.nctu.edu.tw/~chenwj -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180203/81421392/attachment.html>

...e it absolutely *does* become an ABI, where we care about consistency. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5213 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180203/3c4c4877/attachment.bin>

Hi, It's time to prepare the 3.12.6 release, which falls on the 10th of each month, and hence would be 12-02-2018 this time around. This mail is to call out the following, 1) Are there any pending *blocker* bugs that need to be tracked for 3.12.6? If so mark them against the provided tracker [1] as blockers for the release, or at the very least post them as a response to this mail 2)

dear all, i'am working on developing new llvm compiler backend for dlx processor. I finished writing the code and i'm trying to build it. After some errors that i fixed them, i have a one that i can't find a solution for it. I wish you help me to fix it and i will be grateful. Indeed, the compilation stop at level "[ 76%] Building DlxGenAsmMatcher.inc..." with no trace ..

On 02/02/2018 04:27 PM, Chandler Carruth wrote: > On Fri, Feb 2, 2018 at 4:23 PM Chandler Carruth <chandlerc at google.com <mailto:chandlerc at google.com>> wrote: > > On Fri, Feb 2, 2018 at 4:03 PM David Woodhouse <dwmw2 at infradead.org <mailto:dwmw2 at infradead.org>> wrote: > > On Thu, 2018-02-01 at 10:10 +0100, Hans Wennborg via llvm-dev

...n arbitrary string ('StringRef', 'const char*', 'Twine') to an MI with 'BuildMI' or after? Thanks, MartinO -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180203/a559fa8e/attachment.html>

...ormance.rda-cache-limit: 256MB performance.read-ahead: off client.event-threads: 4 server.event-threads: 4 Thank you for any insight. Sincerely, Artem -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20180203/d8ec1baf/attachment.html>

...of an > understatement... > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: smime.p7s > Type: application/x-pkcs7-signature > Size: 5213 bytes > Desc: not available > URL: <http://lists.llvm.org/pipermail/llvm-dev/ > attachments/20180203/1cfad99e/attachment-0001.bin> > > ------------------------------ > > Message: 8 > Date: Fri, 2 Feb 2018 16:17:27 -0800 > From: Galina Kistanova via llvm-dev <llvm-dev at lists.llvm.org> > To: LLVM Dev <llvm-dev at lists.llvm.org>, cfe-commits > <cfe...

Hello Chris, On Thu, 01 Feb 2018 17:00:03 +0000 Chris Murphy <lists at colorremedies.com> wrote: > You can to use efibootmgr for this. NVRAM boot entry is what changed, not > the contents of the EFI System partition. > > efibootmgr -v > > Will list all entries and Boot Order. You need to use --bootorder to make > sure the CentOS entry is first. Interesting.. thanks