similar to: RFC: Adding llvm::ThinStream

Haven't got to this but would like to take a look/review it before it goes in. *skimming over some of the description* Sounds like 'stream' might not be the right terminology - since they return pointers into data that (I think) remains valid for the life of the stream? (this also makes me wonder a bit about memory usage if the cross-block operation is used a lot (causing

Hello, GCC 9.0 introduces a new warning checkers and some of them found possible issues in LLVM. In file included from /home/davidbolvansky/trunk/llvm/include/llvm/Analysis/LazyCallGraph.h:38, from /home/davidbolvansky/trunk/llvm/unittests/Analysis/LazyCallGraphTest.cpp:10: /home/davidbolvansky/trunk/llvm/include/llvm/ADT/ArrayRef.h: In instantiation of

+1, totally a bug. That’s the domain of MutableArrayRef. -Chris > On Oct 1, 2017, at 6:52 AM, David Blaikie via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > +1 seems like a bug > > On Sun, Oct 1, 2017 at 12:35 AM Reid Kleckner via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > It wraps a constant T* and a size_t, so

It wraps a constant T* and a size_t, so I'm surprised std::sort works. It shouldn't. On Sep 30, 2017 5:22 PM, "Daniel Berlin via llvm-dev" < llvm-dev at lists.llvm.org> wrote: It seems like ArrayRefs are supposed to be immutable ( However, as far as i can tell, the iterators are defined wrong to make this true. While ArrayRef<int> Foo(Something); Foo[0] = 5; will

It is suggested in the documentation that if you would have declared a function parameter as SmallVector<Foo,N>&, it is better to instead declare it as SmallVectorImpl<Foo>&. This makes sense, but it seems to me that it is better still to declare it as ArrayRef<Foo>; a quick test suggests it compiles to the same (highly efficient) code, and adds a bit more flexibility in

Hi all, If you don't care about Debug Info or PDB files you can stop reading now. Just wanted to give a heads up that I'm planning to add a new folder under DebugInfo called Msf. MSF stands for Multi-Stream File and is the container format used by PDB debug info files. However, MSF by itself is generic enough that it need not contain PDB data, and in fact I can think of at least one

The latter. Unfortunately we need to get physical access and delete the checkout. I'm afraid reverting will just reintroduce the problem and re-break all the bots that people already took the time to fix, since going from MSF -> Msf is the same as going from Msf -> MSF On Mon, Aug 1, 2016 at 8:55 AM Reid Kleckner <rnk at google.com> wrote: > So, the MSF rename managed to break

I actually regret doing all caps for PDB, and there seems to be mixed use of all caps / rolling caps even with dwarf (some places say DWARF, others say Dwarf). I don't feel too strongly aside from the minor inconvenience of having to change thousands of occurrences where I already used rolling caps though :-/ On Fri, Jul 22, 2016 at 10:52 AM Reid Kleckner <rnk at google.com> wrote:

Hi, I have a CentOS 6.4 fileserver running SerNet Samba 4.0.9 with these global settings (not overridden): read only = No force create mode = 0777 force directory mode = 0777 inherit acls = yes inherit owner = yes inherit permissions = yes On a Windows client, I have Thunderbird 24.0 storing its profile and mail on the Samba share. The

The bot has been failing its CMake step for a while now. Probably fallout from renaming Msf to MSF. Can somebody get this straightened out? It's one of the bots that run VS2013 AFAICT which makes it useful to me. Thanks, --paulr

Is anyone else seeing.... Updated to revision 277264. Summary of conflicts: Tree conflicts: 2 Tree conflict on 'include/llvm/DebugInfo/Msf' > local dir edit, incoming dir delete or move upon update ... Tree conflict on 'lib/DebugInfo/Msf' > local dir edit, incoming dir delete or move upon update in a 'svn update' on llvm trunk? Strangely these errors

Background is that I have been using Evolution for my MUA for a number of years. Migrated to Evolution from Mozilla Mail. I only use Evolution for email and contacts. Getting bored with the issues (frequently not being able to exit and needing to kill it; Bug Buddy popping up in GNOME, etc) that Mark (MHR) and I and I'm sure others have experienced. About 24 hours ago, I installed

On Tue, Jul 26, 2016 at 8:02 AM, Reid Kleckner <rnk at google.com> wrote: > We've been pursuing the direction of writing PDBs from scratch in > llvm/lib/DebugInfo/PDB/Raw and related directories. It might be interesting > to have code that talks to MSPDB140.dll in LLVM, but we really want LLD to > be able to produce its output on any platform. > I completely agree

I hope this problem hasn't been posted before, I cannot find a way to search the archives... I use rsync successfully between several Suse 9.1 machines at my work - never with any problem(s). I had to move my email from an obscure mail client (that saves each message as a separate file) to Mozilla mail (for security purposes). So, my "old" program that I used to sync my mail

Hi, I'm trying to plot a graph with error bars using xYplot in the Hmisc package. My data looks like this. mort stand site type 0.042512776 0.017854525 Plot A ST 0.010459803 0.005573305 PF ST 0.005188321 0.006842107 MSF ST 0.004276068 0.011592129 YSF ST 0.044586495 0.035225266 Plot A LD 0.038810662 0.037355408 PF

We upgraded our imap server hardware and went from dovecot 1.1.3 to 1.2.3 in the process and have been having a critical problem since. I believe I've tracked it down to X-UID reordering that dovecot seemed to do to the mbox format (I know, I know...) inboxes. The problem has manifest itself in several ways with different mail clients but the general problem is that the mail clients have

Rafael Espíndola <rafael.espindola at gmail.com> writes: >> They're obviously related. Endian.h defines types like ulittle32, which >> DTRT when read and written from memory, whereas clang::io has functions >> to read and write memory like so: >> >> void Emit32(raw_ostream& Out, uint32_t V); >> uint32_t ReadLE32(const unsigned char

In planning our migration, I've noticed that lots of users have bits of lint in their ~/mail and/or ~/Mail. For example-- for an mbox called "blah" we may see: blah blah.msf (from Thunderbird) .blah.summary (from... I'm not sure, dtmail maybe) .blah_SIMS_index0003 (from our old IMAP server). When the user goes to

On Tue, Jul 26, 2016 at 12:30 PM, Zachary Turner <zturner at google.com> wrote: > I wrote most of the pdb code in llvm so far. As Reid suggested, if you > look in DebugInfo/PDB/Raw there is a significant amount of code dealing > with msf files and raw pdb streams. If you build the llvm-pdbdump tool you > can run it with the "raw" subcommand to dump lots of low level

Using a fairly simple dovecot config (which obviously needs some max limit tweaking) we have problems with IMAP synchronization between thunderbird clients. Two TB clients in the same IMAP mailbox will, from time to time, show different views of the same INBOX folders, when TB caching is enabled. The only fix is to right-click on the folder, go to "Properties" and use the "Repair