search for: truby

...gt; Hi Medhi > > > > Definitely not expected, the tests should all pass. > > > > As well as what David asked, the verbose output from lit would be helpful > for debugging too. > > > > Thanks for giving it a try. > > Rich > > > > *From:* David Truby <David.Truby at arm.com> > *Sent:* 7 April, 2020 11:49 > *To:* Richard Barton <Richard.Barton at arm.com>; Mehdi AMINI < > joker.eph at gmail.com> > *Cc:* llvm-dev at lists.llvm.org > *Subject:* Re: [llvm-dev] F18 ready to be merged + preview of merge > > >...

...t; Obviously this is a much more invasive change than what you are proposing, > but in my opinion it’s the correct thing to do. > > > > Thanks, > > Christopher Tetreault > > > > *From:* llvm-dev <llvm-dev-bounces at lists.llvm.org> *On Behalf Of *David > Truby via llvm-dev > *Sent:* Thursday, April 9, 2020 7:26 AM > *To:* llvm-dev at lists.llvm.org > *Subject:* [EXT] [llvm-dev] [RFC] Usage of NDEBUG as a guard for > non-assert debug code > > > > Hi all, > > > > During discussions about assertions in the Flang project,...

Hi Mehdi, I can't replicate those failures at my end, could you let me know what OS, compiler and CMake flags you're using so I can try and reproduce? Thanks! David Truby ________________________________ From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Mehdi AMINI via llvm-dev <llvm-dev at lists.llvm.org> Sent: 07 April 2020 06:44 To: Richard Barton <Richard.Barton at arm.com> Cc: llvm-dev at lists.llvm.org <llvm-dev at lists.llv...

...ssibly controlled by another cmake flag (LLVM_ENABLE_DEBUG_CHECKS ?) for code that we want enabled for debugging but not in releases. This would allow LLVM_ENABLE_ASSERTIONS to do what it says on the tin and actually enable assertions only. Does anyone else have any thoughts on this? Thanks David Truby -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200409/5f7af74c/attachment.html>

...being merged into LLVM with these issues still in-flight? Obviously we remain committed to solving them after merging into LLVM? If that is all good then, as previously agreed, we want to give folks something more concrete to review and a bit of time to give feedback on it before we commit. David Truby has just now created a preview of what the LLVM project would look like with F18 merged in as flang. The obvious caveat is that both LLVM and F18 are continuing development so there will be additional commits on both sides of the real merge when it happens. Here is the merge preview: https://githu...

Hey everybody, I've just merged my TextField hacking into master. It's basically a big refactoring and test addition thing, to get signals and variables report something sane. It's not complete yet, but I wanted to have it in, so we don't get too many merge conflicts when Pekka fixes the HTML parsing bugs. Here's a partial list of what's missing so far: - vertical

Hi Eric, Old flang certainly uses C-style strings but f18 uses std::string with few exceptions. Most of the instances in f18 of “char *” aren’t really strings in the C sense – they’re not null terminated and are really just pointers into raw or cooked source files/streams. I can’t think of an instance where the compiler dynamically allocates an array of characters and uses it as a C string. -

Hello everyone, The release branch for LLVM 11 was created from the trunk at 2e10b7a39b930ef8d9c4362509d8835b221fbc0a, and the trunk version was bumped to 12.0.0. Release blockers are tracked by https://llvm.org/PR46725 Please mark any bugs, old or new, that need to be fixed before the release as blocking that bug. Please keep me in the loop via email on any bugs, commits, or other issues that

FWIW I'm a fan of using open-source stuff for open-source projects. Discourse looks open source, but Discord doesn't as far as I can tell (?). On Mon, Nov 18, 2019 at 3:15 AM Chandler Carruth via cfe-dev < cfe-dev at lists.llvm.org> wrote: > Hello folks, > > I sent the message quoted below to llvm-dev@ just now, but it applies to > the whole community so sending an FYI