search for: cc'd

I'm subscribed to llvm-bugs and I get those messages. But, I'm not seeing emails for comments added to bugs I'm cc'd on (e.g. PR24923). I've checked my email preferences and AFAICT I should be getting them. I've checked the two company-supplied filters I'm aware of and they're not catching anything. bugzilla-daemon at llvm.org is on my safe-senders list. Anybody else having this issue? Can...

(This is bcc'd to a list of people who have had problems with rgl lately or who are known to be big users; not cc'd, so you don't all get cc'd all the responses on the R-devel list). I've just put together a test build of rgl, and put it on my web site as http://www.stats.uwo.ca/faculty/...

...rsion was subsequently incremented to 5.0.0 (as per the new versioning scheme [1]). Release blockers are tracked by http://llvm.org/PR31622 Please mark any bugs, old or new, that you think need to be fixed before the release as blocking that. Please help me out in staying on top of the release by cc'ing me on any bugs, commits, or other issues you think may be relevant. If I'm not cc'd on it, there's a large chance I'll miss it. I'm on IRC too, but email is more reliable. If you know of any committs that occurred close to the branch that need to be reverted or merged,...

Dear everyone, It's not quite time to start the 3.8 release process, but it's time to start planning. Please let me know if you want to help with testing and building release binaries for your favourite platform. (If you were a tester on the previous release, you're cc'd on this email.) I propose the following schedule for the 3.8 release: - 13 January: Create 3.8 branch. Testing Phase 1: RC1 binaries built and tested, bugs fixed. Any almost-complete features need to be wrapped up or disabled on the branch ASAP, and definitely before this phase ends. - 27...

Hi Bill, > I'm trying it on 4.0. On 4.2, I'm getting this problem during bootstrapping: > > ccAMeZbg.s:111:non-relocatable subtraction expression, > "___gxx_personality_v0" minus "L0" > ccAMeZbg.s:111:symbol: "___gxx_personality_v0" can't be undefined in a > subtraction expression this is the darwin assembler that barfs, right? It looks like it do...

...le, which would be a shame because hash works well for our needs. Notes: - the code doesn't appear to call exit (it does call abort), and so seems to be suitable for a library - hash-pjw which we also use is already licensed as LGPLv2+ - it looks like the original author was Jim Meyering (CC'd) - the dependencies are all LGPLv2+ Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~r...

...the new versioning scheme [1]). >> >> Release blockers are tracked by http://llvm.org/PR31622 Please mark >> any bugs, old or new, that you think need to be fixed before the >> release as blocking that. >> >> Please help me out in staying on top of the release by cc'ing me on >> any bugs, commits, or other issues you think may be relevant. If I'm >> not cc'd on it, there's a large chance I'll miss it. I'm on IRC too, >> but email is more reliable. >> >> If you know of any committs that occurred close to the...

...----------------------------------------------------------------------- > > It should be similar for cfe and the others. > > The current git mirror branch for llvm seems to only have one commit, > and that's one I just made: > > $ git log --oneline origin/release_40 > 817cc1a7301 Merging r291863: > ------------------------------------------------------------------------ > r291863 | chapuni | 2017-01-12 16:17:15 -0800 (Thu, 12 Jan 2017) | 1 > line > > Note that it doesn't have any parent! > > On Fri, Jan 13, 2017 at 9:23 AM, Hans Wennborg <h...

On 4 February 2017 at 02:58, Sean Silva via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I think that LLD is going to be included in the 4.0 release. At least, we've > been cherry-picking fixes into the release branch. I've CC'd some others > that will know the details. The test-release.sh script still doesn't have it and I believe it's just because we never had it, but I agree we should release it this time. It's good enough to at least be considered beta in some arches and experimental in others. C...

On Thu, May 24, 2007 at 12:46:41PM +0200, BeN [F1233 121D3R] wrote: > I had successfully accessed the svn repository. I had commit everything > for a new release including the new win32 driver. I need is to know if > there is some kind of official way for xiph release ? So release packages go in https://svn.xiph.org/releases/ao/ Update the MD5SUMS and SHA1SUMS checksum...

On 01/05/2007 7:21 AM, Stephan wrote: > Hi, > >> 0x10L > returns: int 0 > > I would expect: int 16? > This happens with all integer constants given by hexadecimal notation. > It's a bug? Certainly looks like one; I've cc'd this to the bug list (but won't be able to look into fixing it). Duncan Murdoch > > >> sessionInfo() > R version 2.5.0 (2007-04-23) > i386-pc-mingw32 > > locale: > LC_COLLATE=German_Germany.1252;LC_CTYPE=German_Germany.1252;LC_MONETARY=German_Germany.1252;...

...activated my active membership of the mailing lists (I am still subscribed for posting, but not for receipt). Of course, I will still be available to help, where I can, with specific questions about my drivers (belkinunv, usbhid-ups) or the configure/automake system. But such mails will have to be cc'd to me directly from now on, as I will no longer receive the list postings. Thanks to everyone for the great team spirit that has made this such an enjoyable project to work on! Best, -- Peter

...g this. I've added a > bug > for the issue: > > http://llvm.org/bugs/show_bug.cgi?id=3324 > > There is currently no Backend: XCore component in bugzilla so I've put > it under new-bugs. Could someone add this component for me. Added. You should also be automatically CC'd on anything filed to that component, -Chris

Hi Renato, > > I'm trying to add pseudo 64-bit load and store instructions for AArch64, which > > should have latencies set to "1" while being otherwise exactly the same as > > normal load and store instructions. > > Can I ask why would you need that? This is the only way I found to stop Machine Instruction Scheduler from reordering load and store

...gs, old or new, that you think need to be fixed before the release as blocking that. Please help out with the release by notifying me of any bugs, commits, or other issues you think might be relevant; ideally by marking them as blockers of the bug above. If it's not on that bug, or I'm not cc'd on an email about it, I'll probably miss it. To get a change committed to the branch, first commit it to trunk as usual, and then request it to be merged -- ideally by filing a blocker bug on PR33849, or by cc'ing me on the commit email. What's next? Once the branch is in good s...

...ther new or already in the tracker) that you think need to be fixed before the release, please mark them as blocking this bug. To get a change committed on the branch, first commit it to trunk as usual, then reply to the commit message on the mailing list with myself and the appropriate code owner CC'd, asking for the change to be merged to the branch. Release notes for 3.8 should be committed directly to the branch, or sent to me in an email and I'll do it for you. If you made any non-trivial changes in the last six months (or know someone else who did), please make sure they get ment...

...d until then > is there a snapshot of the 2.7 documentation anywhere online? >From the homepage, If you go on docs, there's a red message pointing you to here: http://llvm.org/releases/ Which contains downloads, release notes and the docs for every release. > (PS. Please don't cc me on replies. I'm on the list, I don't need two > copies.) Your mail client should know better... Mine does. ;) You're not being CC'd, the list is... -- cheers, --renato http://systemcall.org/ Reclaim your digital rights, eliminate DRM, learn more at http://www.defectivebyd...

...the release notes are highly encouraged, and should be committed directly to the branch. - All other patches should be approved by the release manager (me) and the appropriate code owner. To get a change merged, commit it to trunk, and then reply to the commit email with myself and the code owner cc'd, asking for approval. - Fixes to complete existing features may be merged. However, the features must be completed before Phase II of testing starts, otherwise they should be disabled. If you recently committed something experimental to trunk, please make sure it's disabled on the branch...

...ause the LLVM in HPC workshop will be in Austin on Nov. 15th (http://llvm-hpc2-workshop.github.io/), we'll have an anomalously-high density of LLVM developers in Austin that day. I think it would be a great evening to have an LLVM social! I'm not familair with the Austin area, but I've cc'd some folks who are (or at least were) in Austin, so hopefully we can get some local advice. Please let me know if you'd be interested in attending and/or can provide location suggestions. -Hal -- Hal Finkel Assistant Computational Scientist Leadership Computing Facility Argonne Nation...

...k> writes: > If Rusty agrees, I'd like to add it for 3.16 with a stable marker. Really stable? It improves performance, which is nice. But every patch which goes into the kernel fixes a bug, improves clarity, improves performance or adds a feature. I've now seen all four cases get CC'd into stable. Including some of mine explicitly not marked stable which get swept up by enthusiastic stable maintainers :( Is now there *any* patch short of a major rewrite which shouldn't get cc: stable? Cheers, Rusty.