similar to: [LLVMdev] Reminder: Review LLVM docs

Tanya, > Please finish all documentation review by Friday, May 18th. I think "protected visibility" and "hidden visibility and external weak linkage" are things from "one class". It's not good to put them in separate "classes". External weak linkage and hidden visibility, in fact are not llvm-gcc features. They are at LLVM level. -- With best

What, the deadline is tomorrow?!? The deadline for proposals snuck up on me, and I'm sure many of you forgot as well. Therefore, I am extending the deadline. I have received some great talk proposals, so keep them coming. However, I have very few tutorials, BoFs, posters, or lightening talk proposals. So please, get those proposals in and lets make this year the best developer meeting yet!

Yes, I am working on it. The sub-projects are still having issues but the other documentation has been fixed. -Tanya > On Feb 14, 2019, at 3:53 AM, Alexander Kornienko <alexfh at google.com> wrote: > > Tanya, friendly ping. > > On Mon, Feb 11, 2019 at 3:21 PM Alexander Kornienko <alexfh at google.com <mailto:alexfh at google.com>> wrote: > Hi Tanya, >

Thank you! It seems like new changes in .rst files are picked up quickly now. -- Alex On Thu, Feb 14, 2019 at 7:33 PM Tanya Lattner <tonic at nondot.org> wrote: > This should all be fixed now. > > Thanks, > Tanya > > > On Feb 14, 2019, at 9:50 AM, Tanya Lattner <tonic at nondot.org> wrote: > > Yes, I am working on it. The sub-projects are still having

Hi, The link "Broken versions of GCC and other tools" on http://llvm.org/docs/ReleaseNotes.html points to #brokengcc, where it should point to http://llvm.org/docs/GettingStarted.html#brokengcc I guess. -- Matthieu Moy http://www-verimag.imag.fr/~moy/

I expect llvm.org to need another 30 minutes of downtime. Thank you for your patience. Thanks, Tanya On Apr 25, 2013, at 10:16 AM, Tanya Lattner <lattner at apple.com> wrote: > Just a reminder that llvm.org will be rebooted in 15 minutes, and will be down for about 30 minutes or less. It will be rebooted a couple times so you might see it come up and go back down, but do not get

> On Monday 02 February 2009 13:20, Tanya M. Lattner wrote: >> Just a reminder, I'll be re-creating the 2.5 branch tonight at 9pm PST. > > What does re-creating mean? Why can't the previously-created 2.5 branch > simply be updated? It means deleting the branch and creating a new one. > I ask because svn history will look a little wierd and it makes it harder for

Reminder: The plan is to create the 3.6 branch next week, on 14 January. Please help get the release notes and other documents updated. For example, both the LLVM [1] and Clang [2] release notes look pretty empty. Also, if you'd like to volunteer to be a release tester, please let me know. Cheers, Hans 1. http://llvm.org/docs/ReleaseNotes.html 2.

No. The demo is using 2.3. I update it personally after every release. Yes, it incorrectly says llvm2cpp, but its really using llc. I'll change this when I update it. The ReleaseNotes in TOT are for 2.4. -Tanya On Oct 17, 2008, at 10:52 PM, Óscar Fuentes wrote: > Throwing this C++ code at the online demo: > > struct S { > double d; > unsigned u; > }; > > S

The release branch has been created and the llvm-gcc mirror updated (thanks Bill!). I will be doing some preliminary testing before I request the help of the community to test the release. During this time, I ask that developers only commit documentation changes to the release branch and email the list with any bug fixes that need to be merged into the release branch. Bug fixes have to be

Just a reminder that llvm.org will be rebooted in 15 minutes, and will be down for about 30 minutes or less. It will be rebooted a couple times so you might see it come up and go back down, but do not get alarmed. Thanks, Tanya

On Feb 12, 2010, at 3:02 PM, Douglas Gregor wrote: > > On Feb 12, 2010, at 8:25 AM, David Greene wrote: > >> On Thursday 11 February 2010 18:17:33 Tanya Lattner wrote: >>> Just a reminder that the 2.7 code freeze is on Feb 21st. >>> >>> All major changes should be committed approximately 1 week before the code >>> freeze to ensure adequate

This is my patch for MSVC 2008 and it was applied by Chris: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20080512/062390.html I tested it and it is ok for the 2.3 release. Razvan ----- Original Message ----- From: "Tanya Lattner" <tonic at nondot.org> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Tuesday, May 20, 2008 7:40 AM

I tested this pre-release on MSVC and I noted that none of the submitted patches (mine or others) were applied. So the llvm 2.3 will not compile out of the box in MSVC? Razvan ----- Original Message ----- From: "Tanya M. Lattner" <tonic at nondot.org> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Monday, May 19, 2008 9:00 PM Subject:

On May 19, 2008, at 9:13 PM, Razvan Aciu wrote: > I tested this pre-release on MSVC and I noted that none of the > submitted > patches (mine or others) were applied. > So the llvm 2.3 will not compile out of the box in MSVC? > Please provide me with a link to the patch(s) that need to be applied (llvm-commits archive email). I only apply patches that have been sent to me and

Just a reminder, please complete your testing by May 21st! Thanks, Tanya ---------- Forwarded message ---------- Date: Tue, 13 May 2008 00:25:41 -0700 From: Tanya Lattner <tonic at nondot.org> To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> Subject: 2.3 Pre-release available for testing LLVMers, The 2.3 pre-release is available for testing:

Just a reminder, I'll be re-creating the 2.5 branch tonight at 9pm PST. -Tanya

On Fri, Feb 12, 2010 at 5:48 PM, Daniel Dunbar <daniel at zuster.org> wrote: > I am definitely in favor of this if it is ok with Tanya. > > I hope to spend some time in the next few weeks on tracking down > miscompiles, and it would be great to get Clang to the > "early-but-usable-beta" stage so it makes sense to roll binaries for > 2.7. > > Tanya, I can

LLVMers, The LLVM 2.2 release code freeze and branch creation is less than 1 month away. All major changes should be commited to svn at least 1 week before the code freeze. As a reminder, here is the complete release schedule (which can also be found on the main page in the right sidebar): Jan 16, 2008: Branch creation/Code Freeze (9PM PST). Jan 18, 2008: First round of pre-release testing

On Monday 02 February 2009 13:20, Tanya M. Lattner wrote: > Just a reminder, I'll be re-creating the 2.5 branch tonight at 9pm PST. What does re-creating mean? Why can't the previously-created 2.5 branch simply be updated? I ask because svn history will look a little wierd and it makes it harder for third parties to track revisions and do merges.