search for: nuanti

...ite off either possibility given that the LLVM value wasn't originally intended for GCC compatibility -- we just spun it that way in the frontend :-) Quentin, thoughts? Alp. > > And thanks for implementing this flag! > > > On Thu, Jun 5, 2014 at 4:00 PM, Alp Toker <alp at nuanti.com > <mailto:alp at nuanti.com>> wrote: > > Hi Kostya, > > Looks like our new clang diagnostic from r210293 has caught a > potential issue in compiler-rt which is now breaking the build due > to -Werror: > > /home/dtoolsbot/build/sanitizer-x...

On 25/06/2014 21:03, Eli Bendersky wrote: > On Wed, Jun 25, 2014 at 10:44 AM, Alp Toker <alp at nuanti.com > <mailto:alp at nuanti.com>> wrote: > > For whatever reason, patches posted to the Phabricator website > still aren't being sent to the mailing list, making it difficult > for us to review them. > > I've raised this issue a couple of times...

On 25/06/2014 21:18, Eli Bendersky wrote: > > > > On Wed, Jun 25, 2014 at 11:10 AM, Alp Toker <alp at nuanti.com > <mailto:alp at nuanti.com>> wrote: > > > On 25/06/2014 21:03, Eli Bendersky wrote: > > On Wed, Jun 25, 2014 at 10:44 AM, Alp Toker <alp at nuanti.com > <mailto:alp at nuanti.com> <mailto:alp at nuanti.com > <mailto:a...

On 11/11/2013 07:37, NAKAMURA Takumi wrote: > 2013/11/10 Alp Toker <alp at nuanti.com>: >> #ifndef NDEBUG >> >> This is the biggest violation. NDEBUG should only ever be used in source >> files. That way if something is crashing we can swap in a debug build >> without rebuilding every single dependent application. Win! > I wish; > > -...

On 11 December 2013 17:35, Alp Toker <alp at nuanti.com> wrote: > I noticed a few contributors have been landing patches without responding to > my review comments. Oh, that happened to me too, but it turns out you have to press the "clowncopterize" after making comments inlilne, or Phabricator won't publish them. You can see...

On 11/11/2013 19:08, Chris Lattner wrote: > On Nov 11, 2013, at 9:56 AM, Alp Toker <alp at nuanti.com > <mailto:alp at nuanti.com>> wrote: >> Done :-) >> >> The patchset is 532K so I've put it online: >> >> http://www.nuanti.com/tmp/llvm-api-stability/ >> >> The bulk edits are split out and noted. They were refactored with an >>...

...ling lists *until* the technical issue is confirmed resolved. It's really uncool that code is entering ToT through this back-channel -- I appreciate that it might not be intentional, but every single patch that gets committed this way is a real problem for the project. Alp. -- http://www.nuanti.com the browser experts

On 11/12/2013 17:48, Renato Golin wrote: > On 11 December 2013 17:35, Alp Toker <alp at nuanti.com> wrote: >> I noticed a few contributors have been landing patches without responding to >> my review comments. > Oh, that happened to me too, but it turns out you have to press the > "clowncopterize" after making comments inlilne, or Phabricator won't > pub...

On Nov 11, 2013, at 9:56 AM, Alp Toker <alp at nuanti.com> wrote: > Done :-) > > The patchset is 532K so I've put it online: > > http://www.nuanti.com/tmp/llvm-api-stability/ > > The bulk edits are split out and noted. They were refactored with an internal tool, so it's not a big hassle to keep this up to date unti...

On 30/01/2014 22:57, Daniel Berlin wrote: > On Thu, Jan 30, 2014 at 2:34 PM, Alp Toker <alp at nuanti.com> wrote: >> On 30/01/2014 22:06, Daniel Berlin wrote: >>> Actually, the policy actually says the right thing, you removed a >>> sentence, which says: >>> "Please contact the oversight group for more details." >> >> To be clear, I didn...

...I think it's perfectly realistic to get that number down to 0. We can start by putting a check like that in the build system, first to emit a warning, and ultimately to make violations a build error. This is something we can start working towards today. Any objections? Alp. -- http://www.nuanti.com the browser experts -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131110/c19aa42c/attachment.html>

...to get ToT tree building and running, with the previous commit being in December. So it's clear that a test suite, even a small one, isn't going to just "show up" through casual effort. As such I'd like to propose that we set aside a few days, perhaps with developers from Nuanti and Intel and anyone else who wants to lend a hand, to adapt a branch of the libgomp test suite to be hosted externally, that can be used to regression test the LLVM OpenMP runtime. This shouldn't be much work given that the libraries are ABI/API-compatible and will at least show a way forw...

On Mon, May 5, 2014 at 10:47 AM, Chandler Carruth <chandlerc at google.com>wrote: > On Mon, May 5, 2014 at 8:11 AM, Alp Toker <alp at nuanti.com> wrote: > >> I suspect that pulling in clang header fixes r201729, r202911 and r207606 >> to 3.4.1 will resolve libstdc++ / glibc compatibility issues people have >> been having with 3.4: >> >> r201729: Teach Clang to provide ::max_align_t in C11 and C++11...

....com> wrote: > I don't think it's all patches. I've had plenty of patches go up and > get reviewed with the reviews going to the list lately. > > I'm going to object to this proposal. > > -eric > > On Wed, Jun 25, 2014 at 10:44 AM, Alp Toker <alp at nuanti.com> wrote: >> For whatever reason, patches posted to the Phabricator website still aren't >> being sent to the mailing list, making it difficult for us to review them. >> >> I've raised this issue a couple of times in the last few weeks. >> >> In pr...

On 26/02/2014 09:03, David Chisnall wrote: > On 25 Feb 2014, at 23:13, Alp Toker <alp at nuanti.com> wrote: > >> Now that we've kick-started the LLVM OpenMP runtime discussion, I want to make a concrete proposal to get a test suite up and running for the LLVM OpenMP runtime. I don't think the current setup as an LLVM subproject is sustainable going forward without some for...

On 11/11/2013 19:16, Alp Toker wrote: > On 11/11/2013 19:08, Chris Lattner wrote: >> On Nov 11, 2013, at 9:56 AM, Alp Toker <alp at nuanti.com >> <mailto:alp at nuanti.com>> wrote: >>> Done :-) >>> >>> The patchset is 532K so I've put it online: >>> >>> http://www.nuanti.com/tmp/llvm-api-stability/ >>> >>> The bulk edits are split out and noted. They w...

...00, Alp Toker wrote: > > On 05/05/2014 20:51, Richard Smith wrote: > > On Mon, May 5, 2014 at 10:47 AM, Chandler Carruth > > <chandlerc at google.com <mailto:chandlerc at google.com>> wrote: > > > > On Mon, May 5, 2014 at 8:11 AM, Alp Toker <alp at nuanti.com > > <mailto:alp at nuanti.com>> wrote: > > > > I suspect that pulling in clang header fixes r201729, r202911 > > and r207606 to 3.4.1 will resolve libstdc++ / glibc > > compatibility issues people have been having with 3.4: >...

...at it sort of works, but I don't think we could support it without testing. We could test linking Release clang to Debug LLVM (heck, that probably works, ODR problems aside). [1] http://llvm.org/docs/CodingStandards.html#assert-liberally On Sun, Nov 10, 2013 at 5:42 AM, Alp Toker <alp at nuanti.com> wrote: > With the recent thread on using C++11 in LLVM/clang, one of the recurring > themes was a desire to make the internal headers more consumable. > > While I don't personally want any kind of stability guarantee for internal > headers, I do think we can do more to...

2013/11/10 Alp Toker <alp at nuanti.com>: > #ifndef NDEBUG > > This is the biggest violation. NDEBUG should only ever be used in source > files. That way if something is crashing we can swap in a debug build > without rebuilding every single dependent application. Win! I wish; - NDEBUG may not modify API. class...

On 17/07/2014 20:27, Eric Christopher wrote: > Hi Alp, > > On Thu, Jul 17, 2014 at 6:25 AM, Alp Toker <alp at nuanti.com> wrote: >> Hi Manuel, >> >> Here's another commit authored through the web interface where no discussion >> or reviewership information is apparent on the mailing list. > If you look at the phab review, it's the same there. Does that mean no review comment...