Displaying 6 results from an estimated 6 matches for "pr123".
2006 Mar 22
2
Shared namespaces - solved
Heh heh heh. Whoops.
I've spent a few hours digging around in the source and nearly posted a kludge of a patch I'd written to give a kind of half-baked attempt at getting group-usable subscriptions files. Then I came across something in the source........
In the config file, do something like the following:
namespace public {
separator = /
prefix = Public/
location =
2007 Apr 06
0
[LLVMdev] llc assertion failure
On Fri, 2007-04-06 at 14:27 -0500, Ryan M. Lefever wrote:
> Is a PR a bug report on the bugzilla database?
Yes, so named because of the URL translation. I.e. http://llvm.org/PR123
takes you to bugzilla bug 123. PR == Problem Report.
> I am also running
> bugpoint to see if that yields anything.
Okay, good. That might turn up something useful. If you suspect its a
bug, please file the stack trace and reduced test case in a new PR.
Thanks, Ryan.
Reid.
>
> Re...
2007 Apr 06
2
[LLVMdev] llc assertion failure
Is a PR a bug report on the bugzilla database? I am also running
bugpoint to see if that yields anything.
Reid Spencer wrote:
> Hi Ryan,
>
> On Fri, 2007-04-06 at 13:34 -0500, Ryan M. Lefever wrote:
>
>>I am running the following llvm-ld command to produce native code:
>>
>>llvm-ld -native -o code.exe code.bc -lm
>>
>>However, I am getting the
2016 May 17
2
[RFC] Helping release management
...(like resolved
> and fixed with a revision number) when some keywords are set (like fixes
> PR#). The idea with Diffusion is to have a field that marks the commit has
> been a fix and that we could manually set if we forgot to set the keyword at
> commit time.
A commit that "Fixes PR123" does not necessarily close it. There may
be multiple commits, or we may wait until the buildbots are happy to
close it (I certainly do).
I think that the update here is simpler than that: Whenever a commit
refers a PR, update the bug saying "commit rNNNN was marked as a fix
to this bug&...
2014 Feb 13
2
[LLVMdev] Bad test health
..., 'TODO', 'Todo',
'XXX', 'NOTE', 'Note', 'Bug', 'Fix', 'Shrink', 'http', 'vim', 'IMPORTANT',
'NB', 'WARNING'
]
self.ignored_regs = [
re.compile(r"^PR\d+$"), # PR123
re.compile(r"^(dr|DR)\d+$"), # DR123
re.compile(r"^([A-Z]+[a-z]+)+$"), # FooBar
re.compile(r"^[a-z]+([_-][a-z]+[0-9]*)+$"), # foo_bar
re.compile(r"^[a-z]+[0-9]*$"), # foo
re.compile(r"^[A-Z]$"), # foo
re.compile(r...
2016 May 05
4
[RFC] Helping release management
Filing a PR for *every* fix is overkill. But filing a PR to express "please merge this to the branch" (if there isn't already a PR) seems reasonable.
--paulr
From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Reid Kleckner via llvm-dev
Sent: Thursday, May 05, 2016 10:09 AM
To: Quentin Colombet
Cc: llvm-dev
Subject: Re: [llvm-dev] [RFC] Helping release