search for: tetreault

On Thu, Jun 18, 2020 at 3:37 PM Chris Tetreault <ctetreau at quicinc.com> wrote: > We’re talking about verbose output right? Verbose isn’t the default. > I'm fairly certain the issue in this thread is just the verbosity of -dump-input=fail. Yes, -vv makes it even more verbose by annotating input lines with good matches, etc.,...

...be done here. This majorly affects e.g. Mesa. Joerg ----- Forwarded message from Joerg Sonnenberger via llvm-commits <llvm-commits at lists.llvm.org> ----- Date: Sun, 10 May 2020 02:34:12 +0200 From: Joerg Sonnenberger via llvm-commits <llvm-commits at lists.llvm.org> To: Christopher Tetreault <ctetreau at quicinc.com>, Christopher Tetreault <llvmlistbot at llvm.org> Cc: llvm-commits at lists.llvm.org Subject: Re: [llvm] 2dea3f1 - [SVE] Add new VectorType subclasses Reply-To: Joerg Sonnenberger <joerg at bec.de> On Wed, Apr 22, 2020 at 08:59:20AM -0700, Christopher Tet...

Hi Chris, On Thu, Jun 18, 2020 at 1:37 PM Chris Tetreault via llvm-dev < llvm-dev at lists.llvm.org> wrote: > The thing I use normally only shows the first N lines by default (I don’t > know off hand what N is). Honestly, I don’t feel very strongly about the > specific order, but it’s not useful when somebody proposes something on the >...

...his only reports success/failure, and doesn't show any cause for failure , so I run it in verbose mode with: bin/llvm-lit -a ../llvm/test/CodeGen/my_test.ll In a terminal, the new default behaviour of FileCheck has become pretty unusable IMHO. ________________________________ From: Chris Tetreault <ctetreau at quicinc.com> Sent: 18 June 2020 20:49 To: Joel E. Denny <jdenny.ornl at gmail.com> Cc: Sjoerd Meijer <Sjoerd.Meijer at arm.com>; llvm-dev at lists.llvm.org <llvm-dev at lists.llvm.org> Subject: RE: [llvm-dev] FileCheck Sjoerd specifically said “in verbose mode...

...onnenberger via llvm-commits <llvm-commits at lists.llvm.org<mailto:llvm-commits at lists.llvm.org>> ----- Date: Sun, 10 May 2020 02:34:12 +0200 From: Joerg Sonnenberger via llvm-commits <llvm-commits at lists.llvm.org<mailto:llvm-commits at lists.llvm.org>> To: Christopher Tetreault <ctetreau at quicinc.com<mailto:ctetreau at quicinc.com>>, Christopher Tetreault <llvmlistbot at llvm.org<mailto:llvmlistbot at llvm.org>> Cc: llvm-commits at lists.llvm.org<mailto:llvm-commits at lists.llvm.org> Subject: Re: [llvm] 2dea3f1 - [SVE] Add new VectorType s...

...can have 1 test-case in 1 file, and the current behaviour is already inconvenient, so don't see that as a solution. Cheers. ________________________________ From: Mehdi AMINI <joker.eph at gmail.com> Sent: 19 June 2020 09:32 To: Sjoerd Meijer <Sjoerd.Meijer at arm.com> Cc: Chris Tetreault <ctetreau at quicinc.com>; Joel E. Denny <jdenny.ornl at gmail.com>; llvm-dev at lists.llvm.org <llvm-dev at lists.llvm.org> Subject: Re: [llvm-dev] FileCheck On Fri, Jun 19, 2020 at 12:56 AM Sjoerd Meijer via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists....

...you disagree that this is a big deal, I’ve worked on projects previously where you would get dinged in code review for setting executable permissions on source files. It would be hugely annoying to have to remember to fixup the permissions every time you invoke clang-format. Thanks, Christopher Tetreault From: Adrian McCarthy <amccarth at google.com> Sent: Monday, April 20, 2020 8:36 AM To: Chris Tetreault <ctetreau at quicinc.com> Cc: LLVM Dev <llvm-dev at lists.llvm.org>; cfe-dev at lists.llvm.org Subject: [EXT] Re: [llvm-dev] clang-format sets executable permission on windows...

...bpage? I looked at some build bots today/yesterday that now also show this, and yeah, it's fine either way, I was guessing. My primary use-case is usage in a terminal, and displaying the errors first followed by all input makes this pretty unusable. ________________________________ From: Chris Tetreault <ctetreau at quicinc.com> Sent: 18 June 2020 17:34 To: Sjoerd Meijer <Sjoerd.Meijer at arm.com> Cc: llvm-dev at lists.llvm.org <llvm-dev at lists.llvm.org> Subject: RE: [llvm-dev] FileCheck For anybody viewing these failures through some sort of CI system, showing the error firs...

...n it: * If we want to limit ourselves to CMake versions supported by LTS releases of distros, which distros should we consider, and how far back should we go (i.e. is it just the latest LTS or the last two LTS versions)? From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Chris Tetreault via llvm-dev <llvm-dev at lists.llvm.org> Reply-To: Chris Tetreault <ctetreau at quicinc.com> Date: Wednesday, April 8, 2020 at 12:51 PM To: Eric Christopher <echristo at gmail.com> Cc: "llvm-dev at lists.llvm.org" <llvm-dev at lists.llvm.org> Subject: Re: [llvm-de...

...ng the minimum-requirement too often. FInally, I think we should put the decision of when such an upgrade is judged valuable into the hands of those who are spending the most time working on the build system. We do not need to redo this discussion every time. On Wed, Apr 8, 2020 at 4:36 PM Chris Tetreault via llvm-dev < llvm-dev at lists.llvm.org> wrote: > We should decide who we consider the major distros to be. In my mind this > is Ubuntu, Debian, Fedora, and CentOS/RHEL. We should also consider Visual > Studio releases and whatever OSX and the major BSD’s have. (I honestly have &g...

...n around somewhere. > > If I use GnuWin32’s `ls` to look at files, they (mostly) don’t have > Execute on my system, so I think it’s not git itself setting x permission. > > --paulr > > > > *From:* cfe-dev <cfe-dev-bounces at lists.llvm.org> *On Behalf Of *Chris > Tetreault via cfe-dev > *Sent:* Monday, April 20, 2020 12:32 PM > *To:* Adrian McCarthy <amccarth at google.com> > *Cc:* LLVM Dev <llvm-dev at lists.llvm.org>; cfe-dev at lists.llvm.org > *Subject:* Re: [cfe-dev] [llvm-dev] clang-format sets executable > permission on windows (open...

...to build on diverse environments is a feature, and make a good-faith attempt to support it if reasonable 3. Please gosh no “setup.sh” I support bumping the minimum CMake version. I don’t support a policy of unconditionally bumping the minimum CMake version periodically. Thanks, Christopher Tetreault From: Eric Christopher <echristo at gmail.com> Sent: Thursday, April 9, 2020 4:18 PM To: Philip Reames <listmail at philipreames.com> Cc: Alexandre Ganea <alexandre.ganea at ubisoft.com>; Shoaib Meenai <smeenai at fb.com>; Reid Kleckner <rnk at google.com>; James Y Kn...

...significant one. Can we perhaps reach out and find out the likelihood of a reasonably soonish update there? Linux distros are probably less of a problem - while we all can't use ppas we should be able to do something, similarly with osx. Thoughts? -eric On Wed, Apr 8, 2020 at 9:53 AM Chris Tetreault via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > A line has to be drawn in the sand somewhere. How many “easy” things are > we going to require the user to do? Today it’s build a specific CMake from > source. What’s next? > > > > Not having to manually track...

One of the MSVC devs recently said they are pushing for getting cmake 3.17.0 in the next point release which is expected in May. https://www.reddit.com/r/cpp/comments/fluibz/_/fl2bpz1 On Wed, Apr 8, 2020, 21:51 Chris Tetreault via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Visual studio 2019 ships with CMake 3.15.5, which is pretty darn new IMO. > From what I can tell, CMake versions are tied to visual studio releases. So > assuming we go with “what do recent LTS distros have” as our metric, I > t...

On Thu, Apr 9, 2020 at 9:59 AM Chris Tetreault via llvm-dev < llvm-dev at lists.llvm.org> wrote: > David, > > > > In my opinion, NDEBUG is one of those gross old C things that everybody > complains about. It’s called “Not Debug”, but really it means “Assert > Disabled”. I think one could be forgiven for actually u...

...ng the minimum-requirement too often. FInally, I think we should put the decision of when such an upgrade is judged valuable into the hands of those who are spending the most time working on the build system. We do not need to redo this discussion every time. On Wed, Apr 8, 2020 at 4:36 PM Chris Tetreault via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote: We should decide who we consider the major distros to be. In my mind this is Ubuntu, Debian, Fedora, and CentOS/RHEL. We should also consider Visual Studio releases and whatever OSX and the major BSD’s h...

...s. However, the LLVM IR language only has one pointer type. The LLVM IR language has two types of vectors, and I think it’s reasonable to model them as a class hierarchy in this manner. I’m not familiar with the clang::PointerType situation, so I cannot pass judgement on it. Thanks, Christopher Tetreault From: John McCall <rjmccall at apple.com> Sent: Thursday, May 21, 2020 1:47 PM To: Chris Tetreault <ctetreau at quicinc.com> Cc: llvm-dev at lists.llvm.org Subject: [EXT] Re: [llvm-dev] [RFC] Refactor class hierarchy of VectorType in the IR On 21 May 2020, at 16:01, Chris Tetreault w...

...ar, you don’t require sudo. (I understand that there may be restrictions around running arbitrary executables downloaded from the internet, which of course make sense, but I wanted to clarify that you don’t need to sudo.) From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Chris Tetreault via llvm-dev <llvm-dev at lists.llvm.org> Reply-To: Chris Tetreault <ctetreau at quicinc.com> Date: Thursday, March 26, 2020 at 2:06 PM To: "ldionne at apple.com" <ldionne at apple.com> Cc: "llvm-dev at lists.llvm.org" <llvm-dev at lists.llvm.org>, Libc++...

...FInally, I think we should put the decision of when such an > upgrade is judged valuable into the hands of those who are > spending the most time working on the build system. We do not need > to redo this discussion every time. > > On Wed, Apr 8, 2020 at 4:36 PM Chris Tetreault via llvm-dev > <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > > We should decide who we consider the major distros to be. In > my mind this is Ubuntu, Debian, Fedora, and CentOS/RHEL. We > should also consider Visual...

...hink would be a reasonable period of time for it to be deprecated? 2 weeks? I would also like to add that assuming you have integrated https://reviews.llvm.org/rG2dea3f129878e929e5d1f00b91a622eb1ec8be4e, you should probably start fixing up usages of getNumElements() now. thanks, Christopher Tetreault -----Original Message----- From: Nicolai Hähnle <nhaehnle at gmail.com> Sent: Tuesday, May 5, 2020 4:23 AM To: Chris Tetreault <ctetreau at quicinc.com> Cc: LLVM Dev <llvm-dev at lists.llvm.org> Subject: [EXT] Re: [llvm-dev] [Update][RFC] Refactor class hierarchy of VectorType in...