search for: 2fcfe

...________________________ > cfe-dev mailing list > cfe-dev at lists.llvm.org > https://protect2.fireeye.com/v1/url?k=a2f27696-fe267d28-a2f2360d-86742d02e7e2-ee8f0271cf8b963f&q=1&e=1c901fd6-5221-4af3-a0ab-4a124a098487&u=https%3A%2F%2Flists.llvm.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fcfe-dev

...gt;> >>>> _______________________________________________ >>>> cfe-dev mailing list >>>> cfe-dev at lists.llvm.org >>>> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2flist >>>> s.llvm.org%2fcgi-bin%2fmailman%2flistinfo%2fcfe-dev&data=01%7c01%7ca >>>> ndya%40microsoft.com%7ce71168aad7ca4c98ee1f08d2cb024bf8%7c72f988bf86 >>>> f141af91ab2d7cd011db47%7c1&sdata=9uOfIMd1%2b2DesS3Bne%2f2jkbDpV5REzk >>>> VYj33rujvMGY%3d >>>> >>> >>> >>> ______...

Thanks for the link! There’s some code there that looks extremely relevant to say the least. > On 1 Oct 2015, at 19:00, Hayden Livingston <halivingston at gmail.com> wrote: > > Maybe looking at their code might help: > > https://github.com/dotnet/llilc/blob/dd12743f9cdb5418f1c39b2cd756da1e8396a922/lib/Jit/LLILCJit.cpp#L299 > > On Thu, Oct 1, 2015 at 10:45 AM, David

Hello, Le 29/08/2019 à 01:02, Artem Dergachev a écrit : > Yay thx! > > Sylvestre, is there anything i can help you with in order to get the reports page back up? Sorry, it took me a while to get that back but here is the report of r371718: https://llvm.org/reports/scan-build/ > I'd also indeed love to spam people with warnings that they introduced, even if in the form of a

..._________________________________________ >>>>>> cfe-dev mailing list >>>>>> cfe-dev at lists.llvm.org >>>>>> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2flist >>>>>> s.llvm.org%2fcgi-bin%2fmailman%2flistinfo%2fcfe-dev&data=01%7c01%7ca >>>>>> ndya%40microsoft.com%7ce71168aad7ca4c98ee1f08d2cb024bf8%7c72f988bf86 >>>>>> f141af91ab2d7cd011db47%7c1&sdata=9uOfIMd1%2b2DesS3Bne%2f2jkbDpV5REzk >>>>>> VYj33rujvMGY%3d >>>>>> >>>&gt...

Hi, We're getting ready to start migrating to GitHub. SVN will be moved to read-only now and we'll begin the process of turning on GitHub commit access. I'll send an email when we're done. -Tom

...>>>>> cfe-dev mailing list >> >>>>>> cfe-dev at lists.llvm.org >> >>>>>> >> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2flist >> >>>>>> s.llvm.org >> %2fcgi-bin%2fmailman%2flistinfo%2fcfe-dev&data=01%7c01%7ca >> >>>>>> ndya%40microsoft.com >> %7ce71168aad7ca4c98ee1f08d2cb024bf8%7c72f988bf86 >> >>>>>> >> f141af91ab2d7cd011db47%7c1&sdata=9uOfIMd1%2b2DesS3Bne%2f2jkbDpV5REzk >> >>>>>> VYj33rujvMG...

...sts.llvm.org> >> >>>>>> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2flist <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2flist> >> >>>>>> s.llvm.org <http://s.llvm.org/>%2fcgi-bin%2fmailman%2flistinfo%2fcfe-dev&data=01%7c01%7ca >> >>>>>> ndya%40microsoft.com <http://40microsoft.com/>%7ce71168aad7ca4c98ee1f08d2cb024bf8%7c72f988bf86 >> >>>>>> f141af91ab2d7cd011db47%7c1&sdata=9uOfIMd1%2b2DesS3Bne%2f2jkbDpV5REzk >> >>>>>&gt...

Hello, This is an RFC for adding intrinsics which perform saturating signed/unsigned left shift. There is currently a patch on Phabricator here: https://reviews.llvm.org/D83216 The intrinsics are of the form i32 @llvm.sshl.sat.i32(i32, i32) i32 @llvm.ushl.sat.i32(i32, i32) <4 x i32> @llvm.sshl.sat.v4i32(<4 x i32>, <4 x i32>) <4 x i32>

...____________________________________________ cfe-dev mailing list cfe-dev at lists.llvm.org<mailto:cfe-dev at lists.llvm.org> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev<https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2flists.llvm.org%2fcgi-bin%2fmailman%2flistinfo%2fcfe-dev&data=01%7c01%7cDave.Bartolomeo%40microsoft.com%7c75ae1ecd7082445faf8e08d2e2416634%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=4pXxP9lxo1XdnIaeGB555hQ1KALGHthcRm7an1oagXQ%3d> _______________________________________________ LLVM Developers mailing list llvm-dev at lists.llvm.org<ma...

Definitely having someone who knows both formats well would be an advantage. Dave B might be in the best position to do this, so hopefully he can provide a couple more examples of areas where he has trouble expressing CV information entirely in the backend. Regardless of what everyone ends up deciding on with regards to the front-end / back-discussion, I want to suggest separating the work into

RFC: CodeView debug info emission in Clang/LLVM Overview On Windows, the de facto debug information format is CodeView, most commonly encountered in the form of a .pdb file. This is the format emitted by the Visual C++, C#, and VB.NET compilers, consumed by the Visual Studio debugger and the Windows debugger (WinDbg), and exposed for read-only access via the DIA SDK. The CodeView format has never