Erick Tryzelaar
2006-Aug-23 16:56 UTC
[LLVMdev] updating the "Getting Started" page with more info about the gcc4 frontend
Hello, It looks like the "Getting Started" is missing some info about the gcc 4.0 frontend. Since it doesn't follow the setup of the cfrontend/gcc3.4 package, a couple sections describing the front end don't cover the gcc4 package. Here are the couple things I'd wish could be fleshed out a bit more: Under "Getting Started Quickly (A Summary)", it'd be nice if the section 4 could also have an example for gcc4. Since that package doesn't include a "fixheaders" script, it's unclear whether or not there's anything that I need to do after I extract the code. Under "Getting Started With LLVM", section "Terminology and Notation", the description of "LLVMGCCDIR" should be extended to also say "or where ever the gcc4 binary package was extracted to", or something similar. The section "Install the GCC Front End" doesn't reference the gcc4 packages, so it'd be nice if some info was added. Also, a sentence or two on if it's possible to use both the gcc3.4 and the gcc4 packages at the same time, and how to do it if it's doable. Hopefully, this isn't too unreasonable at this point in time. It'd really help out someone with little experience with llvm get started. Thanks! -e
Scott Michel
2006-Aug-24 01:38 UTC
[LLVMdev] updating the "Getting Started" page with more info about the gcc4 frontend
There should also be a large notice in 40 point font and bold that says, "gcc4 does not produce byte code by default: you must use the -emit-llvm flag to get LLVM byte code." Erick Tryzelaar wrote:> Hello, > > It looks like the "Getting Started" is missing some info about the gcc > 4.0 frontend. Since it doesn't follow the setup of the cfrontend/gcc3.4 > package, a couple sections describing the front end don't cover the gcc4 > package. Here are the couple things I'd wish could be fleshed out a bit > more: > > Under "Getting Started Quickly (A Summary)", it'd be nice if the section > 4 could also have an example for gcc4. Since that package doesn't > include a "fixheaders" script, it's unclear whether or not there's > anything that I need to do after I extract the code. > > Under "Getting Started With LLVM", section "Terminology and Notation", > the description of "LLVMGCCDIR" should be extended to also say "or where > ever the gcc4 binary package was extracted to", or something similar. > > The section "Install the GCC Front End" doesn't reference the gcc4 > packages, so it'd be nice if some info was added. Also, a sentence or > two on if it's possible to use both the gcc3.4 and the gcc4 packages at > the same time, and how to do it if it's doable. > > Hopefully, this isn't too unreasonable at this point in time. It'd > really help out someone with little experience with llvm get started. > Thanks! > > -e > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
Emil Mikulic
2006-Aug-24 02:00 UTC
[LLVMdev] updating the "Getting Started" page with more info about the gcc4 frontend
On Wed, Aug 23, 2006 at 06:38:36PM -0700, Scott Michel wrote:> There should also be a large notice in 40 point font and bold that says, > "gcc4 does not produce byte code by default: you must use the -emit-llvm > flag to get LLVM byte code."=) Where -is- that documented? The only reason I know about it is because of how many times it's come up on the list. =) (Which doesn't help people who don't read the list) --Emil
Possibly Parallel Threads
- [LLVMdev] updating the "Getting Started" page with more info about the gcc4 frontend
- [LLVMdev] updating the "Getting Started" page with more info about the gcc4 frontend
- [LLVMdev] updating the "Getting Started" page with more info about the gcc4 frontend
- [LLVMdev] updating the "Getting Started" page with more info about the gcc4 frontend
- [LLVMdev] updating the "Getting Started" page with more info about the gcc4 frontend