similar to: 'git llvm push' not working for me on Windows

Usually every time I've seen that error message, it's been related to line ending normalization. But James is right, I did use it successfully this morning as well as yesterday. On Mon, Nov 19, 2018 at 1:03 PM James Y Knight via llvm-dev < llvm-dev at lists.llvm.org> wrote: > It does sound like I must've broken something, but I believe zturner used > it on windows

FTR the commit where it failed for me had both llvm and clang changes. I wonder if that contributed. --paulr From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of via llvm-dev Sent: Monday, November 19, 2018 6:01 PM To: zturner at google.com; jyknight at google.com Cc: llvm-dev at lists.llvm.org Subject: Re: [llvm-dev] 'git llvm push' not working for me on Windows Hm.

I've verified that none of the files I tried to check in had Windows-style line endings. It's something else. --paulr From: vsk at apple.com [mailto:vsk at apple.com] On Behalf Of Vedant Kumar Sent: Thursday, November 22, 2018 9:38 AM To: Robinson, Paul Cc: zturner at google.com; jyknight at google.com; llvm-dev at lists.llvm.org Subject: Re: [llvm-dev] 'git llvm push' not working

Can you please run "git llvm --verbose push" and send me the output? BTW, I've just committed a fix for the handling of binary patch data when you're running it under python3.X. I don't believe that was a regression from my recent changes, but if you're using python3, you could see if that fixes it for you. On Tue, Nov 27, 2018 at 7:20 PM Mikhail Ramalho via llvm-dev

OK, I've managed to do it: I was trying to push it from a build/ directory, maybe that's why the git apply was failing. Pushing the commit from the root of the repo worked. Em qua, 28 de nov de 2018 às 16:40, Mikhail Ramalho < mikhail.ramalho at gmail.com> escreveu: > Hi, > > The patch only changes one file in clang. Here's the patch: >

Poking around in the .git\llvm-upstream-svn tree, I find that llvm\trunk\test\DebugInfo\Generic is empty, as are all the other subdirectories of test\DebugInfo that I tried. I have other files in the checkin that are in leaf directories but those files all exist. I hacked git-llvm to add a –verbose option: `git apply --verbose -p2 -` returned 1 Checking patch

Excellent, thanks! --paulr From: James Y Knight [mailto:jyknight at google.com] Sent: Thursday, November 29, 2018 12:00 PM To: Robinson, Paul Cc: Mikhail Ramalho; vedant_kumar at apple.com; llvm-dev Subject: Re: [llvm-dev] 'git llvm push' not working for me on Windows Aha! From your output I figured out what I screwed up. Sorry about the trouble... Illustration of the issue: svn

The usual workaround is to do `rm –rf .git/llvm-upstream-svn` and try again. You could also patch llvm/utils/git-svn/git-llvm to add the `--verbose` option to the `git apply` command, which would provide better diagnostic output. HTH, --paulr From: Petr Hosek [mailto:phosek at chromium.org] Sent: Wednesday, January 30, 2019 10:52 PM To: Robinson, Paul Cc: James Y Knight; llvm-dev; vedant_kumar at

Well, apparently clang has clang::StringLiteral in clang/AST/Expr.h So, our options are either: Allow this name clash (obviously the namespaces don't clash, only the names) and deal with it when it's an issue (which will be limited to clang, and even then not very often), or choose a different name. Thoughts? On Mon, Dec 12, 2016 at 11:53 AM Zachary Turner <zturner at google.com>

Hi, What could be wrong or missing in the debug info (using DIBuilder) so that a parameter is displayed well in the "Locals" window but "not found" when typing it in the "Watch" window (and not displayed in the Auto) ? Thanks ! -------------- next part -------------- An HTML attachment was scrubbed... URL:

AFAICT this appears to be the first time you've clarified that you're talking about a situation where the compile-time checking happens using something other than format strings. In Pavel's original email, he suggested compile time checking and you mentioned that I didn't object to it. But if you go back and read my response, I said we can do the compile time checking *of the

On Mon, Dec 12, 2016 at 1:03 PM Zachary Turner via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Well, apparently clang has clang::StringLiteral in clang/AST/Expr.h > > So, our options are either: Allow this name clash (obviously the > namespaces don't clash, only the names) and deal with it when it's an issue > (which will be limited to clang, and even then not

On Wed, Oct 12, 2016 at 10:13 AM James Y Knight <jyknight at google.com> wrote: > > > I wonder what use cases you envision for this? Why does LLVM need a super > extensible flexible formatting library? I mean -- if you were developing > this as a standalone project, that seems like maybe a nice feature. But I > see no rationale as to why LLVM should include it. > We

This looks like you're using the wrong repository. The 'git llvm' command only works with the new repository layout. Please clone https://github.com/llvm/llvm-project/ instead. *From: *Ryan Taylor via llvm-dev <llvm-dev at lists.llvm.org> *Date: *Tue, May 14, 2019 at 2:18 PM *To: * <paul.robinson at sony.com> *Cc: *llvm-dev It's both "No such file or

Do you still see this if you use lld-link for linking? The "corrupt obj file" is something we saw on chrome's bots every now and then before we switched to lld. On Mon, Nov 19, 2018 at 5:27 PM Zachary Turner <zturner at google.com> wrote: > +Nico Weber <thakis at google.com> > > On Mon, Nov 19, 2018 at 12:25 PM via llvm-dev <llvm-dev at lists.llvm.org>

On Wed, Oct 12, 2016 at 12:40 PM Mehdi Amini <mehdi.amini at apple.com> wrote: > On Oct 12, 2016, at 12:35 PM, Zachary Turner <zturner at google.com> wrote: > > You get compile time checking automatically when we can use c++14 though. > If you use it with a string literal, you'll get compile time checking, > otherwise you won’t. > > > I understand that, but

> On Dec 12, 2016, at 3:45 PM, David Blaikie via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > > On Mon, Dec 12, 2016 at 1:03 PM Zachary Turner via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > Well, apparently clang has clang::StringLiteral in clang/AST/Expr.h > > So, our options are either: Allow this name

I can. I'll whip something up today On Fri, Dec 9, 2016 at 1:18 AM Malcolm Parsons <malcolm.parsons at gmail.com> wrote: > On 2 December 2016 at 17:12, James Y Knight <jyknight at google.com> wrote: > > +1 from me for the StringLiteral proposal from a few messages back. > > Zachary, do you want to commit StringLiteral? > > -- > Malcolm Parsons >

I don't feel like I can unilaterally declare this topic closed, since there was an objection to that last time. But with no additional feedback after another week, I'd still really like to close this out, and start moving forward with the original plan, again... On Mon, Nov 26, 2018 at 2:28 PM James Y Knight <jyknight at google.com> wrote: > It's been a week and a half more

On Thu, Dec 13, 2018 at 5:54 AM James Y Knight via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Fri, Nov 16, 2018 at 7:40 PM Jeremy Lakeman <Jeremy.Lakeman at gmail.com> wrote: >> >> Semantic versioning would recommend "v8.0.0-dev", "v8.0.0-rc1" etc. The hyphen indicating that this is a pre-release version coming before "v8.0.0"