search for: filemanag

...llvm we found the file system abstractions in clang/llvm to be one of the points that could be nicer to integrate with. I’m writing this mail to propose a strawman and get some feedback on what you guys think the right way forward is (or whether we should just leave things as they are). First, the FileManager we have in clang has helped us a lot for our tooling - when we run clang in a mapreduce we don’t need to lay out files on a disk, we can just map files into memory and happily clang over them. We’re also using the same mechanism to map builtin includes; in short, the FileManager has made it possi...

...n clang/llvm to be one of the points that could be nicer >> to integrate with. I’m writing this mail to propose a strawman and get >> some feedback on what you guys think the right way forward is (or >> whether we should just leave things as they are). >> >> First, the FileManager we have in clang has helped us a lot for our >> tooling - when we run clang in a mapreduce we don’t need to lay out >> files on a disk, we can just map files into memory and happily clang >> over them. We’re also using the same mechanism to map builtin >> includes; in shor...

...could be nicer >>>> to integrate with. I’m writing this mail to propose a strawman and get >>>> some feedback on what you guys think the right way forward is (or >>>> whether we should just leave things as they are). >>>> >>>> First, the FileManager we have in clang has helped us a lot for our >>>> tooling - when we run clang in a mapreduce we don’t need to lay out >>>> files on a disk, we can just map files into memory and happily clang >>>> over them. We’re also using the same mechanism to map builtin &g...

...ne of the points that could be nicer >>> to integrate with. I’m writing this mail to propose a strawman and get >>> some feedback on what you guys think the right way forward is (or >>> whether we should just leave things as they are). >>> >>> First, the FileManager we have in clang has helped us a lot for our >>> tooling - when we run clang in a mapreduce we don’t need to lay out >>> files on a disk, we can just map files into memory and happily clang >>> over them. We’re also using the same mechanism to map builtin >>> i...

...> abstractions in clang/llvm to be one of the points that could be nicer > to integrate with. I’m writing this mail to propose a strawman and get > some feedback on what you guys think the right way forward is (or > whether we should just leave things as they are). > > First, the FileManager we have in clang has helped us a lot for our > tooling - when we run clang in a mapreduce we don’t need to lay out > files on a disk, we can just map files into memory and happily clang > over them. We’re also using the same mechanism to map builtin > includes; in short, the FileManag...

...ad various thoughts in this direction as well (although no implementation). See: http://lists.cs.uiuc.edu/pipermail/cfe-dev/2010-July/009903.html for my RFC from last year (focused at bug reporting, but involved defining a VFS layer). My one main implementation level comment is I don't think FileManager is the right API layer to abstract at (it is too specific to Clang's usage, and too hard to propagate through the rest of LLVM). My intuition is that it is better to set out to define a lower level VFS layer that is rich enough to support everything we do and the vagaries of Win32/Unix, but i...

.../009903.html >> for my RFC from last year (focused at bug reporting, but involved >> defining a VFS layer). > > Cool, that sounds like another use case very similar to our replaying > at scale use case. > >> My one main implementation level comment is I don't think FileManager >> is the right API layer to abstract at (it is too specific to Clang's >> usage, and too hard to propagate through the rest of LLVM). My >> intuition is that it is better to set out to define a lower level VFS >> layer that is rich enough to support everything we do a...

...;>>>> to integrate with. I’m writing this mail to propose a strawman and get >>>>> some feedback on what you guys think the right way forward is (or >>>>> whether we should just leave things as they are). >>>>> >>>>> First, the FileManager we have in clang has helped us a lot for our >>>>> tooling - when we run clang in a mapreduce we don’t need to lay out >>>>> files on a disk, we can just map files into memory and happily clang >>>>> over them. We’re also using the same mechanism to ma...

...du/pipermail/cfe-dev/2010-July/009903.html > for my RFC from last year (focused at bug reporting, but involved > defining a VFS layer). Cool, that sounds like another use case very similar to our replaying at scale use case. > My one main implementation level comment is I don't think FileManager > is the right API layer to abstract at (it is too specific to Clang's > usage, and too hard to propagate through the rest of LLVM). My > intuition is that it is better to set out to define a lower level VFS > layer that is rich enough to support everything we do and the vagaries...

...ne of the points that could be nicer >>> to integrate with. I’m writing this mail to propose a strawman and get >>> some feedback on what you guys think the right way forward is (or >>> whether we should just leave things as they are). >>> >>> First, the FileManager we have in clang has helped us a lot for our >>> tooling - when we run clang in a mapreduce we don’t need to lay out >>> files on a disk, we can just map files into memory and happily clang >>> over them. We’re also using the same mechanism to map builtin >>> i...

...t could be nicer >>>> to integrate with. I’m writing this mail to propose a strawman and get >>>> some feedback on what you guys think the right way forward is (or >>>> whether we should just leave things as they are). >>>> >>>> First, the FileManager we have in clang has helped us a lot for our >>>> tooling - when we run clang in a mapreduce we don’t need to lay out >>>> files on a disk, we can just map files into memory and happily clang >>>> over them. We’re also using the same mechanism to map builtin &g...

...;>>>> to integrate with. I’m writing this mail to propose a strawman and get >>>>> some feedback on what you guys think the right way forward is (or >>>>> whether we should just leave things as they are). >>>>> >>>>> First, the FileManager we have in clang has helped us a lot for our >>>>> tooling - when we run clang in a mapreduce we don’t need to lay out >>>>> files on a disk, we can just map files into memory and happily clang >>>>> over them. We’re also using the same mechanism to ma...

...; to integrate with. I’m writing this mail to propose a strawman and get >>>>>> some feedback on what you guys think the right way forward is (or >>>>>> whether we should just leave things as they are). >>>>>> >>>>>> First, the FileManager we have in clang has helped us a lot for our >>>>>> tooling - when we run clang in a mapreduce we don’t need to lay out >>>>>> files on a disk, we can just map files into memory and happily clang >>>>>> over them. We’re also using the same mec...

...grate with. I’m writing this mail to propose a strawman and > get > >>>>> some feedback on what you guys think the right way forward is (or > >>>>> whether we should just leave things as they are). > >>>>> > >>>>> First, the FileManager we have in clang has helped us a lot for our > >>>>> tooling - when we run clang in a mapreduce we don’t need to lay out > >>>>> files on a disk, we can just map files into memory and happily clang > >>>>> over them. We’re also using the same...

Hello! I was trying to optimize our automatically generated backend for Open RISC and for this purpose I went through the gcc torture testsuite. There are many programs that are better optimized by LLVM, but some are much better optimized by gcc 4.9. The main limitations were is loop unrolling and structures handling. Differences can be best seen e.g. when compiling for an

Hi there, I've got two questions, and I'll list them in order of importance. (1) Is there a way, or is there any research/development going into unearthing a way, to mount a samba filesystem like any other filesystem under UNIX? And (2), does anyone know of a good X filemanager? What I would really like to do is be able to mount a Samba directory or resource and treat it like any other directory. That way, I could get away from the FTP-like interface and be able to browse it with a graphical filemanager. Thanks, JP -- Joshua Pincus BS Computer Science, May '9...

On Thu, Jun 12, 2014 at 10:57:46AM +0200, Armin Steinhoff wrote: > > Hi, > > first problem was: > > >FileManager.cpp:311:21: error: range-based ‘for’ loops are not allowed > >in C++98 mode > >for (auto & fe: SeenFileEntries) { > >^ > >FileManager.cpp:312:14: error: request for member ‘getValue’ in ‘fe’, > >which is of non-class type ‘int’ > >if (fe.getValue() == Stale...

...`clang::DiagnosticsEngine::DiagnosticsEngine(llvm::IntrusiveRefCntPtr<clang::DiagnosticIDs> const&, clang::DiagnosticConsumer*, bool)' tutorial1.cpp:(.text+0xf4): undefined reference to `clang::LangOptions::LangOptions()' tutorial1.cpp:(.text+0x125): undefined reference to `clang::FileManager::FileManager(clang::FileSystemOptions const&)' tutorial1.cpp:(.text+0x148): undefined reference to `clang::SourceManager::SourceManager(clang::DiagnosticsEngine&, clang::FileManager&)' tutorial1.cpp:(.text+0x17c): undefined reference to `llvm::sys::getDefaultTargetTriple()'...

...this: > I've got two questions, and I'll list them in order of importance. (1) Is > there a way, or is there any research/development going into unearthing a > way, to mount a samba filesystem like any other filesystem under UNIX? > > And (2), does anyone know of a good X filemanager? What I would really > like to do is be able to mount a Samba directory or resource and treat it > like any other directory. That way, I could get away from the FTP-like > interface and be able to browse it with a graphical filemanager. Answers: 1) There's no need for research; t...

...::DiagnosticsEngine(llvm::IntrusiveRefCntPtr<clang::DiagnosticIDs> > const&, clang::DiagnosticConsumer*, bool)' > tutorial1.cpp:(.text+0xf4): undefined reference to > `clang::LangOptions::LangOptions()' > tutorial1.cpp:(.text+0x125): undefined reference to > `clang::FileManager::FileManager(clang::FileSystemOptions const&)' > tutorial1.cpp:(.text+0x148): undefined reference to > `clang::SourceManager::SourceManager(clang::DiagnosticsEngine&, > clang::FileManager&)' > tutorial1.cpp:(.text+0x17c): undefined reference to > `llvm::sys::get...