llvm/docs/LangRef.html, branch masterhttp://llvm.orghttps://git.amat.us/llvm/atom/docs/LangRef.html?h=master2012-12-07T10:36:55Zdocs: Convert LangRef to reST.2012-12-07T10:36:55ZSean Silvasilvas@purdue.edu2012-12-07T10:36:55Zurn:sha1:f722b007b201a755b06c48eba8a6058972ddf267
NOTE: If you have any patches in the works that modify LangRef, you will
need to rewrite the changes to LangRef.html to their equivalents in
LangRef.rst. If you need assistance feel free to contact me.
Since LangRef is mission-critical for the project and "normative", I
have taken extra care to ensure that no content was lost or altered in
the conversion. The content was converted with a tool called `pandoc`,
so there is no chance for a human error like accidentally forgetting a
sentence or whatever. After the initial conversion by `pandoc`, only
changes to the markup were done.
This is just the most literal conversion of the HTML document as
possible. It might be worth exploring some way to chop up this massive
document into separate pages, e.g. something like
`docs/LangRef/Instructions.rst`, `docs/LangRef/Intrinsics.rst`, etc.
with `docs/LangRef.rst` being an "intro/navigation page" of sorts. On
the other hand, that loses the ability to {Ctrl,Cmd}-F for a given term
right from your browser.
IMO, I think our stylesheet needs some work because I find it hard to
tell what level of nesting some of the headings are at (e.g. "is this a
new section or is it a subsection?"). The issue is present on other
pages, but the sheer size and deep section structure of LangRef really
brings this issue out. If there are any web designers out there in the
community it would be awesome if you tried to come up with something
nicer.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@169596 91177308-0d34-0410-b5e6-96231b3b80d8
Removed redundancy in wording2012-11-30T23:14:52ZMichael Ilsemanmilseman@apple.com2012-11-30T23:14:52Zurn:sha1:5ba39ae563c19e0304387d39fa359305ada6220b
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@169053 91177308-0d34-0410-b5e6-96231b3b80d8
Clean up the documentation to have a common description area for fast-math flags.2012-11-30T23:12:42ZMichael Ilsemanmilseman@apple.com2012-11-30T23:12:42Zurn:sha1:01b3710eae3095f32fb311285d36e8eb2e5bc135
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@169052 91177308-0d34-0410-b5e6-96231b3b80d8
Fast-math flags documentation added to LangRef2012-11-27T00:48:29ZMichael Ilsemanmilseman@apple.com2012-11-27T00:48:29Zurn:sha1:a33e3d75fe761292341871253f86b163df11142c
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@168652 91177308-0d34-0410-b5e6-96231b3b80d8
Correct copy-pasto where we're talking about function attributes and not parameter attributes.2012-11-26T22:04:13ZBill Wendlingisanbard@gmail.com2012-11-26T22:04:13Zurn:sha1:8a66b6ab45986f1fe23b0131ef92b27fd4460ad7
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@168619 91177308-0d34-0410-b5e6-96231b3b80d8
Add the Erlang/HiPE calling convention, patch by Yiannis Tsiouris.2012-11-16T12:36:39ZDuncan Sandsbaldrick@free.fr2012-11-16T12:36:39Zurn:sha1:dc7f174b5e049172f085ff5957f58998bdc446a4
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@168166 91177308-0d34-0410-b5e6-96231b3b80d8
Remove trailing whitespace2012-11-16T00:58:59ZMichael Ilsemanmilseman@apple.com2012-11-16T00:58:59Zurn:sha1:96952bd3b10d6a880b406461e2373b8781abc919
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@168121 91177308-0d34-0410-b5e6-96231b3b80d8
Add missing documentation for llvm.exp2, llvm.log10, and llvm.log2.2012-11-15T07:01:39ZCraig Toppercraig.topper@gmail.com2012-11-15T07:01:39Zurn:sha1:f48ef5594f9bc14effa0928a5628b88286c0592a
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@168026 91177308-0d34-0410-b5e6-96231b3b80d8
Add llvm.ceil, llvm.trunc, llvm.rint, llvm.nearbyint intrinsics.2012-11-15T06:51:10ZCraig Toppercraig.topper@gmail.com2012-11-15T06:51:10Zurn:sha1:490104720db9e1e0eb9cc27e88e2d7288ac27ff0
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@168025 91177308-0d34-0410-b5e6-96231b3b80d8
Relax the restrictions on vector of pointer types, and vector getelementptr.2012-11-13T12:59:33ZDuncan Sandsbaldrick@free.fr2012-11-13T12:59:33Zurn:sha1:2333e29be441d9d55920651e0b2add23ab0c1613
Previously in a vector of pointers, the pointer couldn't be any pointer type,
it had to be a pointer to an integer or floating point type. This is a hassle
for dragonegg because the GCC vectorizer happily produces vectors of pointers
where the pointer is a pointer to a struct or whatever. Vector getelementptr
was restricted to just one index, but now that vectors of pointers can have
any pointer type it is more natural to allow arbitrary vector getelementptrs.
There is however the issue of struct GEPs, where if each lane chose different
struct fields then from that point on each lane will be working down into
unrelated types. This seems like too much pain for too little gain, so when
you have a vector struct index all the elements are required to be the same.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@167828 91177308-0d34-0410-b5e6-96231b3b80d8