similar to: [LLVMdev] [PATCH] use-diet for review

Displaying 20 results from an estimated 3000 matches similar to: "[LLVMdev] [PATCH] use-diet for review"

2008 Apr 30
0
[LLVMdev] [PATCH] use-diet for review
On Apr 29, 2008, at 9:40 AM, Gabor Greif wrote: > Sorry, I relied "svn diff" to include freshly added files. svn add file svn diff . will show it.
2008 Apr 29
0
[LLVMdev] [PATCH] use-diet for review
Hi Gabor, Thanks for posting the memory savings. 13% less memory usage in 447.dealII is very impressive. I haven't taken more than a very brief peek at this patch, but I have a few questions already. Is there a header missing? I don't see DECLARE_TRANSPARENT_OPERAND_ACCESSORS defined anywhere. Also, what affect does this macro have on doxygen? In User.h: +public: + template
2008 Apr 30
2
[LLVMdev] [PATCH] use-diet for review
Mike, Holger, thanks for the tips, but being a long-time subversion user, I already knew this all :-) The problem was that I did an SVN merge from branch to trunk, and I ended up with: ... M include/llvm/User.h A + include/llvm/OperandTraits.h M include/llvm/Instruction.h ... The little "+" after the "A" means, the file got copied unchanged, and I think this is
2008 Apr 29
5
[LLVMdev] [PATCH] use-diet for review
Hi all, I have reported more than enough about the space savings achieved and the associated costs, here comes the current patch for review. Since this one is substantially smaller than the previous one, I did not cut it in pieces. The front part is about headers and the rest the .cpp and other files. Cheers, Gabor -------------- next part -------------- An embedded and charset-unspecified
2008 Apr 29
0
[LLVMdev] [PATCH] use-diet for review
On Apr 29, 2008, at 1:27 AM, Gabor Greif wrote: > Hi all, > > I have reported more than enough about the space savings achieved > and the associated costs, here comes the current patch for review. > > Since this one is substantially smaller than the previous one, I did > not cut it in pieces. The front part is about headers and the rest > the .cpp and other files. Hi
2008 Apr 24
2
[LLVMdev] Status of use-diet so far (NO API CHANGES)
Hi all, in the last days I was busy gathering performance data about the "class Use"-related changes. I have nice measurements on a 8Gig MacPro with kimwitu++. This is important to say, because this machine is in plenty of memory, so swapping is not likely, which means that in more constrained setups (when swapping occurs) the use-diet approach is probably producing even better
2018 Aug 31
2
Extending StoreInst/LoadInst
Hi, I am trying to figure out the best way to add some extra metadata to the store and load llvm-ir instructions: The metadata content is a 'Value*' expression representing a side channel, containing dependency information that is used to help the Scoped Alias Analysis. Optimizations that don't know about this side channel can safely drop it, where the only effect would be on the
2008 Apr 25
0
[LLVMdev] Status of use-diet so far (NO API CHANGES)
On Apr 24, 2008, at 9:03 AM, Gabor Greif wrote: > > As you can see, the use-diet changes actually lower the build time > of kimwitu++! (this is as of yesterday's r50182). > Parity is not only reached, but surpassed. Thanks for these numbers. Do you know how much of this increase is due to co-allocating Use arrays with their users, and how much is due to the actual shrinking of
2007 Feb 09
0
cluster "non-diet", "diet" example.
Suppose, we have 3 people called: Francis, Cedric and Nina. Base on what they have eaten, we want to cluster people by "diet", "non-diet". # original data file, named as filename "food.csv". Francis|potato Francis|chocolate Francis|chocolate Francis|milk Cedric|vegetable Cedric|vegetable Cedric|potato Nina|potato Nina|chocolate Nina|chocolate Nina|potato # Step 1: I
2008 Mar 26
0
[LLVMdev] use-diet design?
Hi Gabor, Could you give a little more detailed description of the plan with the user-diet changes? I read the README but still don't have a good picture of what will happen. Specifically, which operators new/delete will be overridden? What work will they do? How will the surrogate getters/setters work? Thanks, Dan
2008 Mar 26
0
[LLVMdev] use-diet design?
> Hi Gabor, > > Could you give a little more detailed description of the plan > with the user-diet changes? I read the README but still don't > have a good picture of what will happen. > > Specifically, which operators new/delete will be overridden? > What work will they do? How will the surrogate getters/setters > work? > > Thanks, > > Dan
2006 Jan 26
8
switching to edge rails
Hi, I want to start using has_many :through. I think that eventually I''ll be removing all uses has_and_belongs_to_many from my project. Here is my situation I''m using SVN I want to use edge rails Reading the wiki about switching to edge rails[1], I can''t figure out which combination of subsections I must perform. Do I want edge rails to reside in the vendor
2007 Feb 18
2
help with an error with tinymce (installation)
hi, i''m trying to install tinymce following the wiki, so i''ve done svn propedit svn:externals vendor/plugins into the tmp saved tiny_mce <a href="https://secure.near-time.com/svn/plugins/trunk/tiny_mce">https://secure.near-time.com/svn/plugins/trunk/tiny_mce</a> but it say this $ svn propedit svn:externals vendor/plugins svn: Error parsing svn:externals
2012 Jul 13
2
[LLVMdev] [llvm-commits] Dealing with a corrupted /proc/self/exe link
On Fri, Jul 13, 2012 at 1:40 PM, Benjamin Kramer <benny.kra at gmail.com>wrote: > > On 13.07.2012, at 21:39, Gabor Greif <gabor.greif at alcatel-lucent.com> > wrote: > > > Benjamin Kramer wrote: > >> On 13.07.2012, at 09:46, Gabor Greif <gabor.greif at alcatel-lucent.com> > wrote: > >> > >>> Hi all, > >>> >
2008 Apr 15
6
[LLVMdev] PATCH: Use size reduction -- wave2
Hi All, here comes the patch for the second wave of Use class size reduction. I have included all the machinery that is needed, and it is *active*. The User* inside of Use is even sometimes NULL, but the algorithm is able to recover it. If there is a non-null User* present, then I am asserting that it equals the computed value. I did not receive feedback for the algorithmic part yet, so I
2012 Jul 14
0
[LLVMdev] [llvm-commits] Dealing with a corrupted /proc/self/exe link
Chandler Carruth wrote: > On Fri, Jul 13, 2012 at 1:40 PM, Benjamin Kramer <benny.kra at gmail.com > <mailto:benny.kra at gmail.com>> wrote: > > > On 13.07.2012, at 21:39, Gabor Greif <gabor.greif at alcatel-lucent.com > <mailto:gabor.greif at alcatel-lucent.com>> wrote: > > > Benjamin Kramer wrote: > >> On 13.07.2012,
2012 Jul 13
2
[LLVMdev] [llvm-commits] Dealing with a corrupted /proc/self/exe link
Benjamin Kramer wrote: > On 13.07.2012, at 09:46, Gabor Greif <gabor.greif at alcatel-lucent.com> wrote: > >> Hi all, >> >> I am in charge of the controlled introduction of clang into >> our builds at my workplace. Since all our tools must run from >> a ClearCase view for automatic dependency tracking, we have been >> biten by a Linux bug, and
2007 Apr 14
1
[LLVMdev] "Name that compiler"
Looks like people send many names in the contest, so shall I do too. I propose "Lepton", loosely meaning light (featherweight) in Greek. It is used in particle physics to refer to very light particles (electrons, muons). For me it also has the connotations of fastness and restlessness (in the LLVM sense of post-compile optimization). See more at:
2012 Jul 13
0
[LLVMdev] [llvm-commits] Dealing with a corrupted /proc/self/exe link
On 13.07.2012, at 09:46, Gabor Greif <gabor.greif at alcatel-lucent.com> wrote: > Hi all, > > I am in charge of the controlled introduction of clang into > our builds at my workplace. Since all our tools must run from > a ClearCase view for automatic dependency tracking, we have been > biten by a Linux bug, and readlink("/proc/self/exe", ...) gives >
2013 Aug 02
4
Internalization of help pages
Is it possible to translate help files? I see there are some localization options for GUI, but not for help. I think this would be really helpful for users who don't have English as their primary language. Because all the online help is created from text files, it should be not that difficult to maintain different language versions (e.g. to mark them as not valid when primary documentation in