Displaying 20 results from an estimated 20000 matches similar to: "[LLVMdev] [Reminder] 3.3 Patches"
2012 Apr 17
0
[LLVMdev] 3.1 Has Branched
how to get this branch?
still svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm?
Thank you.
On Tue, Apr 17, 2012 at 2:16 PM, Bill Wendling <wendling at apple.com> wrote:
> Hi all,
>
> We branched for the 3.1 release! (Yay!)
>
> If there are any fixes which you think should go into the release, please
> contact the code owners
2012 Apr 17
7
[LLVMdev] 3.1 Has Branched
Hi all,
We branched for the 3.1 release! (Yay!)
If there are any fixes which you think should go into the release, please contact the code owners (http://llvm.org/docs/DeveloperPolicy.html#owners) so that they can approve the patches. No patches will be accepted into the 3.1 release without prior approval!
This should be a great release! :-)
-bw
2011 Oct 21
1
[LLVMdev] LLVM 3.0rc1 Testing Begins!
Not yet. That is, I don't think any have been filed at all for 3.0. I don't know whether to be happy or worried. :-) Any that are regressions should be marked with the 'regression' keyword and be a release blocker.
-bw
On Oct 20, 2011, at 8:40 AM, Jim Grosbach wrote:
> Hi Bill,
>
> Do we have a list of which PRs have been filed that are considered release blockers?
2012 Apr 17
0
[LLVMdev] [cfe-dev] 3.1 Has Branched
What was the revision the branch was made from?
On Apr 16, 2012, at 11:16 PM, Bill Wendling <wendling at apple.com> wrote:
> Hi all,
>
> We branched for the 3.1 release! (Yay!)
>
> If there are any fixes which you think should go into the release, please contact the code owners (http://llvm.org/docs/DeveloperPolicy.html#owners) so that they can approve the patches. No
2013 Feb 06
2
[LLVMdev] Question about changes to llvm::Argument::addAttr(AttributeSet AS) API
On 6 Feb 2013, at 07:50, Bill Wendling wrote:
> On Feb 4, 2013, at 11:54 PM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote:
>
>> On 5 Feb 2013, at 01:32, Bill Wendling wrote:
>>
>>> No. It hasn't been written up. We typically don't do write-ups for API changes. However, we do list the thing we do change in the ReleaseNotes (these changes
2010 Sep 04
0
[LLVMdev] Announcement: LLVM 2.8 Branch Created
The LLVM 2.8 branches have been created! We will be conducting several rounds of testing of this branch during September. See http://llvm.org/ for a tentative schedule.
What this means for you
As I mentioned in a previous e-mail, the branch is still open for code submissions. However there are a few rules that we need to adhere to:
No new features are allowed, no matter how trivial they may be.
2011 Oct 20
0
[LLVMdev] LLVM 3.0rc1 Testing Begins!
Hi Bill,
Do we have a list of which PRs have been filed that are considered release blockers?
-Jim
On Oct 17, 2011, at 4:33 PM, Bill Wendling wrote:
> Hi all,
>
> Testing for LLVM 3.0 release candidate 1 is now under way! We will soon have binaries available for you to download and try. Those who would like to compile things and try them out for themselves can grab the source
2011 Oct 17
3
[LLVMdev] LLVM 3.0rc1 Testing Begins!
Hi all,
Testing for LLVM 3.0 release candidate 1 is now under way! We will soon have binaries available for you to download and try. Those who would like to compile things and try them out for themselves can grab the source tarballs here:
http://llvm.org/pre-releases/3.0/
A Word About Patches
I neglected to send out instructions on how to get patches into the LLVM 3.0 branch. All patches must
2007 Dec 19
2
[LLVMdev] Reminder: LLVM 2.2 code freeze 1 month away
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
2007 Sep 07
0
[LLVMdev] 2.1 Code Freeze reminder
LLVMers,
The 2.1 code freeze and branch creation is next Wednesday, September 12th
at 9PM PDT. At this point in time, any major changes should be checked in.
You are free to still commit changes to the tree, but please be extra
cautious in what you commit and monitor the testers on platforms you are
not able to test on. We would like things to remain as stable as possible
up until the code
2008 Jan 31
0
[LLVMdev] 2.2 Pre-release Testing Reminder
LLVMers,
I just wanted to remind everyone that the 2.2 pre-release testing (round
1) ends tomorrow (2/1/08 midnight). Please send your test results to the
list by that deadline.
Thanks to all who have tested the release so far!
-Tanya
2014 Jun 13
2
[LLVMdev] LLVM 3.5 Pre-Reminder
This is just a reminder that the 3.5 release will be starting up in July. Most likely the 2nd week. Details will come later. But you can help things along.
* Be sure to update the READMEs!
* Try to get your new features in good working condition.
* Tackle some of the bugs in the bugzilla. Focus on mis-compilations.
* And update the READMEs!!
Share and enjoy!
-bw
2008 Apr 04
3
[LLVMdev] choice between SSAPRE and bitvector aporach
On Fri, Apr 4, 2008 at 2:38 AM, Bill Wendling <isanbard at gmail.com> wrote:
> On Apr 2, 2008, at 10:11 PM, Xuehai Qian wrote:
> > Hi LLVMers,
> > I am a PHD student in CS dept in UIUC, I am doing a project for
> > Vikram's course, it is about PRE. I would like to know why you didn't
> > choose SSAPRE in LLVM, since it seems to be more suitable for
2013 Feb 06
0
[LLVMdev] Question about changes to llvm::Argument::addAttr(AttributeSet AS) API
On Feb 4, 2013, at 11:54 PM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote:
> On 5 Feb 2013, at 01:32, Bill Wendling wrote:
>
>> No. It hasn't been written up. We typically don't do write-ups for API changes. However, we do list the thing we do change in the ReleaseNotes (these changes haven't made it there though).
>
> The attributes API has
2011 Feb 28
1
[LLVMdev] [cfe-dev] Reminder: LLVM 2.9 Branching in One Week
Hi Bill,
Will the 2.9 branch be reflected in the git mirrors?
Thanks,
Chad
On Sun, Feb 27, 2011 at 5:43 PM, Bill Wendling <wendling at apple.com> wrote:
> This is a reminder that we will be branching for LLVM 2.9 in one week!
> 07:00:00 p.m. Sunday March 6, 2011 PST / 03:00:00 a.m. Monday March 7, 2011
> GMT
> What this means for you:
> Please keep a watch on all of your
2011 Oct 13
5
[LLVMdev] Reminder: LLVM 3.0 Branching Friday!
This is just a reminder to say that we will be branching for the LLVM 3.0 release Friday!
07:00:00 p.m. Friday October 14, 2011 PDT
02:00:00 a.m. Saturday October 15, 2011 GMT
Now is the time to look at the buildbots and see what fixes they need:
http://lab.llvm.org:8011/console
As of this writing, we have:
• several test failures on llvm-gcc self-host:
2011 Oct 14
0
[LLVMdev] [cfe-dev] Reminder: LLVM 3.0 Branching Friday!
On Oct 14, 2011, at 12:54 PM, David A. Greene wrote:
> greened at obbligato.org (David A. Greene) writes:
>
>> I have some pending patches for 3.0 only.
>
> Of course I meant post-3.0 only.
>
Yes, I'll send out a message when it's okay to submit post-3.0 patches.
-bw
2011 Feb 28
3
[LLVMdev] Reminder: LLVM 2.9 Branching in One Week
This is a reminder that we will be branching for LLVM 2.9 in one week!
07:00:00 p.m. Sunday March 6, 2011 PST / 03:00:00 a.m. Monday March 7, 2011 GMT
What this means for you:
Please keep a watch on all of your patches going into mainline. And pay close attention to the buildbots and fix any issues quickly.
Also, please try to finish up any last minute feature work. While it won't be the
2008 Apr 04
0
[LLVMdev] choice between SSAPRE and bitvector aporach
On Apr 2, 2008, at 10:11 PM, Xuehai Qian wrote:
> Hi LLVMers,
> I am a PHD student in CS dept in UIUC, I am doing a project for
> Vikram's course, it is about PRE. I would like to know why you didn't
> choose SSAPRE in LLVM, since it seems to be more suitable for LLVM (it
> can operate directly on SSA form and avoid the conversion between SSA
> and bit-vector). Can
2009 Feb 24
0
[LLVMdev] [llvm-commits] remove libtool from build system
On Feb 23, 2009, at 8:40 PM, Nick Lewycky wrote:
> For those of you who haven't noticed, I'm planning to commit a major
> change to the Makefile rules tomorrow evening (Tuesday) if there are
> no complaints about it between now and then.
>
> This needs testing on Darwin. I've heard back from Linux on many
> platforms and even FreeBSD, which is fantastic, but