similar to: [LLVMdev] Demo Script Paths

It's already messed with, but there's no harm. If someone turns on the llvm2cpp option, then they get an error message at the bottom of the output page. All other output is normal. So, there's no harm in it. If/when llvm2cpp becomes available on Zion, people then the llvm2cpp output will appear. Note that llvm2cpp is a 1.8 release feature. My change was to help people learning LLVM

> I'm trying to get the demo script to run llvm2cpp so that people can get > familiar with the LLVM C++ API through the online demo. However, it > seems that the path used doesn't include llvm2cpp (not updated in a > while?). The demo script currently uses these paths on Zion: I can look into this, but I would strongly suggest not messing with the demo script until 2-3

The demo script isn't part of the release and its not failing. Do you want me to revert the changes? Reid. On Thu, 2006-08-10 at 10:08 -0700, Tanya M. Lattner wrote: > > It's already messed with, but there's no harm. If someone turns on the > > llvm2cpp option, then they get an error message at the bottom of the > > output page. All other output is normal. So,

> It's already messed with, but there's no harm. If someone turns on the > llvm2cpp option, then they get an error message at the bottom of the > output page. All other output is normal. So, there's no harm in it. > If/when llvm2cpp becomes available on Zion, people then the llvm2cpp > output will appear. Note that llvm2cpp is a 1.8 release feature. My > change was

On Thu, 10 Aug 2006, Tanya M. Lattner wrote: >> The demo script isn't part of the release and its not failing. >> Do you want me to revert the changes? > No. I just said that we should avoid anymore changes for the next 2 weeks to > maintain stability. FWIW, I agree with Tanya on this. People *pound* on the demo page immediately after a release as they try it out and

> The demo script isn't part of the release and its not failing. > > Do you want me to revert the changes? No. I just said that we should avoid anymore changes for the next 2 weeks to maintain stability. -Tanya > > Reid. > > On Thu, 2006-08-10 at 10:08 -0700, Tanya M. Lattner wrote: >>> It's already messed with, but there's no harm. If someone turns on

Okay, let me reiterate. The llvm2cpp option is *already* on the demo script page. If you choose that option, you just get an error message because llvm2cpp can't be found. Its harmless and everything else still works. I won't change the script for a couple of weeks, per Tanya's and your request. Reid. On Thu, 2006-08-10 at 10:48 -0700, Chris Lattner wrote: > On Thu, 10 Aug

On Wed, 9 Aug 2006, Reid Spencer wrote: > At the very least, can we get some modern tools into > gaeke/llvm/Release/bin ? Done. Note that the demo page is giving an llvm2cpp error when used now: llvm2cpp: error opening l2cppFile! llvm2cpp exited with an error. Please correct source and resubmit. I assume that this is a bug in index.cgi. If you want to play with the demo page, go ahead,

Qiuyu, The dynamic optimization project (an internal research project in our group) uses some way to map LLVM basic blocks to native code addresses. If this is what you want, perhaps you can ask Brian Gaeke (gaeke at uiuc.edu) to give you some information about how that is done. --Vikram http://www.cs.uiuc.edu/~vadve http://llvm.cs.uiuc.edu/ On Aug 19, 2004, at 5:11 PM, Misha Brukman

Reid Spencer wrote: 1) It appears that the only problem was with sending email to the llvm-commits list; any files commited to the repository should be commited. 2) The web server error log filled up /var/log, preventing the CVS commit script from sending email. The Apache error log was filled with entries like this: [client 219.140.157.109] PHP Notice: Undefined offset: 1 in

Throwing this C++ code at the online demo: struct S { double d; unsigned u; }; S foo() { return S(); } produces this LLVM C++ API code: (...) PAListPtr func__Z3foov_PAL = 0; { SmallVector<ParamAttrsWithIndex, 4> Attrs; ParamAttrsWithIndex PAWI; PAWI.index = 0; PAWI.attrs = 0 | ParamAttr::NoUnwind; Attrs.push_back(PAWI); PAWI.index = 1; PAWI.attrs = 0 |

All, Commits aren't taking right now because apparently Zion is out of disk space: cvs commit utils/findmisopt Checking in utils/findmisopt; /var/cvs/llvm/llvm/utils/findmisopt,v <-- findmisopt new revision: 1.9; previous revision: 1.8 done Insufficient disk space; try again later Insufficient disk space; try again later returntosender: cannot select queue for llvm Insufficient disk

How big was that log file? If we are running close to the limit, I can just buy a new disk for zion. Other suggestions welcome. --Vikram On Nov 25, 2006, at 12:38 AM, John T. Criswell wrote: > Reid Spencer wrote: > > 1) It appears that the only problem was with sending email to the > llvm-commits list; any files commited to the repository should be > commited. > >

You are correct, ubyte 2 simply means 3rd element of the structure. This quantity is always constant (it specifies the field number), so we could have used any signed or unsigned integer type for it instead of ubyte. UByte means we are limited to at most 256 structure fields but it also makes the bytecode representation more compact. (To remove this restriction, we may migrate to UInt in the

See attached build (gmake -k) log. -- gaeke at uiuc.edu -------------- next part -------------- gmake[1]: Entering directory `/scratch/scratch0/gaeke/llvm-497cz/utils/Burg' gmake[1]: Nothing to be done for `all'. gmake[1]: Leaving directory `/scratch/scratch0/gaeke/llvm-497cz/utils/Burg' gmake[1]: Entering directory `/scratch/scratch0/gaeke/llvm-497cz/lib' gmake[2]: Entering

Brian Gaeke wrote: > > A typo in test/Makefile was the trigger for this problem: > > http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20041101/ > 020216.html > > John, can you please look into this bug some more and add some error > checking to the llvm-specific qmtest python modules to make this error > less severe? Does the fork bomb occur in the

Chris Lattner wrote: > On Fri, 29 Jun 2007, John Criswell wrote: > >> The LLVM web server is up and running, but we're still working on some >> subversion configuration issues. The server may go up and down >> intermittently as we try configuration changes over the next half hour. >> > > Apparently someone clobbered

No. The demo is using 2.3. I update it personally after every release. Yes, it incorrectly says llvm2cpp, but its really using llc. I'll change this when I update it. The ReleaseNotes in TOT are for 2.4. -Tanya On Oct 17, 2008, at 10:52 PM, Óscar Fuentes wrote: > Throwing this C++ code at the online demo: > > struct S { > double d; > unsigned u; > }; > > S

I'd be interested to hear how that's being done - if Brian would reply to the list about it, I'd appreciate it. -mike On Aug 19, 2004, at 3:39 PM, Vikram S. Adve wrote: > Qiuyu, > > The dynamic optimization project (an internal research project in our > group) uses some way to map LLVM basic blocks to native code > addresses. If this is what you want, perhaps you

TSG (our support group) is going to set up a Wiki on zion so that access can be checked against a list of some sort. It should happen by early next week, perhaps sooner (not likely). They actually have a central departmental Wiki and created an LLVM space there already, but that cannot be made accessible to non-UIUC people without creating an account for each person. They have a