search for: isanbard

The third 3.5 release candidate is now available. Please pick up sources and binaries here: https://llvm.org/pre-release/3.5 Run it through its phases and report any bugs you find! Share and enjoy! -bw

On 9/25/07, Daniel Berlin <dberlin at dberlin.org> wrote: > On 9/24/07, Bill Wendling <isanbard at gmail.com> wrote: > > On Sep 24, 2007, at 3:15 PM, Dale Johannesen wrote: > > > > Weird. I see a potential problem, though. The code is like this: > > > > void dumpToDOUT(SparseBitVector<> *bitmap) { > > dump(*bitmap, DOUT); > > } > > &...

Looking forward to these changes! Thanks for working on it. On Fri, Oct 11, 2013 at 10:32 PM, Bill Wendling <isanbard at gmail.com> wrote: > Hi Dmitry, > > I can try my best, but it would be a bit tricky to get it all finished by > then... > > -bw > > On Oct 11, 2013, at 4:10 AM, Dmitry Babokin <babokin at gmail.com> wrote: > > Bill, > > Are there any chances that you...

After several years as LLVM release manager, I’ve decided to step down as release manager. I recently haven’t been able to focus as much time on LLVM development as I should, and I don’t want the releases to suffer because of that. I’ve enjoyed all of the releases I’ve done. We have a great team of testers. And the community as a whole really helps out so that we can produce a great produce. I my

....com> > No. I think that you might want to use Clang for inspiration on design, >> but you'd certainly not be bound to that. If you'd like to take a much more >> start-from-scratch approach, you can also look at the code that Bill put >> together: https://github.com/isanbard/flang - If you use that as a base, >> we can always merge it with the useful lfort pieces later. > > Ok, that's good to know. In the next couple of days I will study the lfort > repository more, and see if I can perhaps contribute a commit or two. > Thankfully I know git and g...

On Wed, Jul 15, 2009 at 3:43 PM, Eli Friedman<eli.friedman at gmail.com> wrote: > On Wed, Jul 15, 2009 at 3:01 PM, Bill Wendling<isanbard at gmail.com> wrote: >> The core problem, in my opinion, is that people *don't* pay attention >> to the build bot failure messages that come along. > > That's largely because of the number of false positives. > There have been fewer and fewer of these in recent times...

On 6/28/19 5:35 PM, James Y Knight via llvm-dev wrote: On Fri, Jun 28, 2019 at 5:53 PM Bill Wendling <isanbard at gmail.com<mailto:isanbard at gmail.com>> wrote: On Fri, Jun 28, 2019 at 1:48 PM James Y Knight <jyknight at google.com<mailto:jyknight at google.com>> wrote: On Fri, Jun 28, 2019 at 3:00 PM Bill Wendling <isanbard at gmail.com<mailto:isanbard at gmail.com>> wrote...

----- Original Message ----- > From: "Alex L" <arphaman at gmail.com> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "Anton Korobeynikov" <anton at korobeynikov.info>, "Bill Wendling" <isanbard at gmail.com>, "LLVM Developers Mailing > List" <llvmdev at cs.uiuc.edu> > Sent: Saturday, April 13, 2013 11:34:43 AM > Subject: Re: [LLVMdev] GSoC project questions. > > > Thanks for your replies. > Working on the lfort compiler would certainly be an inter...

On Jan 3, 2015, at 11:52 PM, Bill Wendling <isanbard at gmail.com> wrote: > On Jan 2, 2015, at 8:32 PM, David Callahan <dcallahan at fb.com> wrote: > >> Hi, >> >> I am new to the LLVM dev community so forgive a perhaps obvious question. I am looking at bug 17623 which is an LTO/optimizer interaction bug. I am wor...

On 9/25/07, Bill Wendling <isanbard at gmail.com> wrote: > On 9/25/07, Daniel Berlin <dberlin at dberlin.org> wrote: > > On 9/24/07, Bill Wendling <isanbard at gmail.com> wrote: > > > On Sep 24, 2007, at 3:15 PM, Dale Johannesen wrote: > > > > > > Weird. I see a potential problem, th...

...2012 CDT (13 days, 16 hours ago) Log Message: Creating release_31 branch Here is how I fixed this in my local git repo: looking at the last commit to trunk r155049, before the "new release_31" has been created: commit bdcfb7663a2a62fd52a14dbeaa076423c719ec2d Author: Bill Wendling <isanbard at gmail.com> Date: Wed Apr 18 21:38:12 2012 +0000 Add a flag to rebranch if we need to. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk at 155049 91177308-0d34-0410-b5e6-96231b3b80d8 and the first commit that appears on the release_31 branch: commit 0d2807ae7060f6b0ffdf65...

...il/llvmdev/2013-October/066389.html Please read and let me know you comments. -bw On Oct 11, 2013, at 2:47 PM, Dmitry Babokin <babokin at gmail.com> wrote: > Looking forward to these changes! Thanks for working on it. > > > On Fri, Oct 11, 2013 at 10:32 PM, Bill Wendling <isanbard at gmail.com> wrote: > Hi Dmitry, > > I can try my best, but it would be a bit tricky to get it all finished by then... > > -bw > > On Oct 11, 2013, at 4:10 AM, Dmitry Babokin <babokin at gmail.com> wrote: > >> Bill, >> >> Are there any chance...

> > No. I think that you might want to use Clang for inspiration on design, > but you'd certainly not be bound to that. If you'd like to take a much more > start-from-scratch approach, you can also look at the code that Bill put > together: https://github.com/isanbard/flang - If you use that as a base, > we can always merge it with the useful lfort pieces later. Ok, that's good to know. In the next couple of days I will study the lfort repository more, and see if I can perhaps contribute a commit or two. Thankfully I know git and github and so that would...

...he opt command. Error opening '../../../build/Release/lib/LLVMExecutionEngine.o': ../../../build/Release/lib/LLVMExecutionEngine.o: only ET_DYN and ET_EXEC can be loaded -load request ignored. Any ideas?? Please help me out here. Thanks, Bhavani --- On Sun, 10/26/08, Bill Wendling <isanbard at gmail.com> wrote: > From: Bill Wendling <isanbard at gmail.com> > Subject: Re: [LLVMdev] Error while creating ExecutionEngine > To: bhavi63 at yahoo.com, "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> > Date: Sunday, October 26, 2008, 6:46 AM > O...

...fails because of mailing Frontend tests, and I have had continues failures of some DejaGNU tests for a long time on some builders. Its not a false positive per se, but one starts to ignore the failures because they aren't unexpected. - Daniel On Wed, Jul 15, 2009 at 4:10 PM, Bill Wendling<isanbard at gmail.com> wrote: > On Wed, Jul 15, 2009 at 3:43 PM, Eli Friedman<eli.friedman at gmail.com> wrote: >> On Wed, Jul 15, 2009 at 3:01 PM, Bill Wendling<isanbard at gmail.com> wrote: >>> The core problem, in my opinion, is that people *don't* pay attention >&...

----- Original Message ----- > From: "Alex L" <arphaman at gmail.com> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "Anton Korobeynikov" <anton at korobeynikov.info>, "Bill Wendling" <isanbard at gmail.com>, "LLVM Developers Mailing > List" <llvmdev at cs.uiuc.edu> > Sent: Friday, April 19, 2013 12:17:16 PM > Subject: Re: [LLVMdev] GSoC project questions. > Hi again, > > I was studying and building the lfort repository as I said I would > do, but...

...Unknown command line argument '-verify-di'. Try: 'bin/opt -help' opt: Did you mean '-verify'? On 1/5/15, 1:16 PM, "Duncan P. N. Exon Smith" <dexonsmith at apple.com<mailto:dexonsmith at apple.com>> wrote: On 2015-Jan-05, at 01:14, Bill Wendling <isanbard at gmail.com<mailto:isanbard at gmail.com>> wrote: On Jan 3, 2015, at 11:52 PM, Bill Wendling <isanbard at gmail.com<mailto:isanbard at gmail.com>> wrote: On Jan 2, 2015, at 8:32 PM, David Callahan <dcallahan at fb.com<mailto:dcallahan at fb.com>> wrote: Hi, I am n...

On Fri, Jun 28, 2019 at 1:48 PM James Y Knight <jyknight at google.com> wrote: > On Fri, Jun 28, 2019 at 3:00 PM Bill Wendling <isanbard at gmail.com> wrote: > >> On Thu, Jun 27, 2019 at 1:44 PM Bill Wendling <isanbard at gmail.com> wrote: >> >>> On Thu, Jun 27, 2019 at 1:29 PM James Y Knight <jyknight at google.com> >>> wrote: >>> >>>> I think this is fine, except...

Have you been sleeping poorly worried about the Clang 3.5 release? Well, this may help! The plan right now is to start testing in July with August as the target release month. There isn’t a schedule yet, of course. But it should be a goodly amount of time for all y’all to prepare for the release process. If you have any questions, please let me know. If you’d like to volunteer to be a tester,

...Log Message:    Creating release_31 branch > > > Here is how I fixed this in my local git repo: looking at the last > commit to trunk r155049, before the "new release_31" has been created: > > commit bdcfb7663a2a62fd52a14dbeaa076423c719ec2d > Author: Bill Wendling <isanbard at gmail.com> > Date:   Wed Apr 18 21:38:12 2012 +0000 > >    Add a flag to rebranch if we need to. > >    git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk at 155049 > 91177308-0d34-0410-b5e6-96231b3b80d8 > > and the first commit that appears on the release_31 bra...