similar to: [LLVMdev] detab llvm

A user has table-formatted data which contains accents and finds it problematic that his tables misalign after going through Markdown. This is because he made them align using tab characters and Markdown will convert these to spaces even in pre-formatted text and Markdown is not multi-byte aware. This raises two questions: 1. Should Markdown convert tabs to spaces in pre-formated text?

On Oct 8, 2009, at 5:18 PM, Mike Stump wrote: > On Oct 8, 2009, at 4:52 PM, Stuart Hastings wrote: >> Currently, to get LLVM to build "Apple-style," it's necessary to >> copy two files (utils/buildit/GNUmakefile and utils/buildit/ >> build_llvm) into the top-level directory. > > Why not: > > $ RC_ARCHS="x86" make > echo Apple Build.

On Oct 9, 2009, at 8:40 AM, Stuart Hastings wrote: > > On Oct 8, 2009, at 5:18 PM, Mike Stump wrote: > >> On Oct 8, 2009, at 4:52 PM, Stuart Hastings wrote: >>> Currently, to get LLVM to build "Apple-style," it's necessary to >>> copy two files (utils/buildit/GNUmakefile and utils/buildit/ >>> build_llvm) into the top-level directory.

On Wed, Jul 2, 2008 at 7:00 PM, Mike Stump <mrs at apple.com> wrote: > On Jul 2, 2008, at 4:39 PM, Eli Friedman wrote: >> Another perspective on this sort of issue, if you haven't seen it: >> http://weblogs.mozillazine.org/roc/archives/2007/10/ >> tablua_fracta.html. > > If we apply their logic to llvm, we can dominate, if we just target 8 > cores. :-)

On Tue, Feb 17, 2009 at 2:35 PM, Mike Stump <mrs at apple.com> wrote: > On Feb 17, 2009, at 2:21 PM, Scott Michel wrote: > > - remove trailing whitespace, > > - expand tabs to spaces, > > I'd argue for not changing anything, just fail it. > Trimming whitespace is innocuous, at best. Expanding tabs to spaces, I might be inclined to agree is a 'fail' since

2009/1/28 Mike Stump <mrs at apple.com>: > Author: mrs > Date: Tue Jan 27 20:43:35 2009 > New Revision: 63168 > > URL: http://llvm.org/viewvc/llvm-project?rev=63168&view=rev > Log: > Add a preliminary version number. > > Modified: > cfe/trunk/Driver/clang.cpp > > Modified: cfe/trunk/Driver/clang.cpp > URL:

On Mon, Sep 29, 2008 at 6:30 PM, Mike Stump <mrs at apple.com> wrote: > /* snip */ AMD's CodeAnalyst is free and quite wonderful at this job. Shows details about just about anything the CPU reports (and on newer AMD CPU's there is an even more ridiculous amount of information) about every little function call, time they took, multiple profiling modes, etc...

This patch adds targets to support the installation of clang in isolation. Ok? -------------- next part -------------- A non-text attachment was scrubbed... Name: clang-2.patch Type: application/octet-stream Size: 952 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090119/39061b42/attachment.obj> -------------- next part --------------

Currently, to get LLVM to build "Apple-style," it's necessary to copy two files (utils/buildit/GNUmakefile and utils/buildit/build_llvm) into the top-level directory. This is generally a PITA inside of Apple. (I'll spare you the gory details. :-) I'd like to fix this for Apple, and I want to avoid compromising anybody else's build system. I've never used

On Feb 3, 2009, at 2:35 PMPST, Mike Stump wrote: > On Feb 3, 2009, at 2:28 PM, Kasra wrote: >> I was looking around the LLVM instruction set and I failed to find >> ROL and ROR instructions. Is there any plans on adding these >> instructions to LLVM? > > Not sure what you mean: He's referring to the LLVM IR, I think, and it's true that doesn't have

On May 9, 2008, at 3:10 AM, Nicolas Capens wrote: > Please note that I'm not trying to compile from C code, I try to > generate > functions at run-time directly. I want to keep it target-independent > too, so > I can't use intrinsics either. Ah, but you can use any intrinsic that is target independent.... The gcc vector stuff is meant to work on all targets as I

On Oct 8, 2009, at 4:52 PM, Stuart Hastings wrote: > Currently, to get LLVM to build "Apple-style," it's necessary to > copy two files (utils/buildit/GNUmakefile and utils/buildit/ > build_llvm) into the top-level directory. Why not: $ RC_ARCHS="x86" make echo Apple Build. Apple Build. $ make echo Standard Build Standard Build $ cat Makefile ifneq

I'm seeing a build failure... In file included from /Volumes/mrs5/net/llvm/llvm/lib/VMCore/ Attributes.cpp:14: /Volumes/mrs5/net/llvm/llvm/include/llvm/Attributes.h: In member function 'llvm::Attributes llvm::AttrListPtr::getParamAttributes(unsigned int) const': /Volumes/mrs5/net/llvm/llvm/include/llvm/Attributes.h:152: error: 'assert' was not declared in this scope

The input language is at assembly level, and the location akin to a %temp ( a virtual register if you will) and contains moves from one virtual to another. Though these are not like memory but I could represent them as local variables and do loads and stores; so I dont know how to represent it in C except as local variables. On Thu, May 28, 2009 at 4:06 PM, Mike Stump <mrs at apple.com>

On Thu, Jul 3, 2008 at 9:09 AM, Devang Patel <dpatel at apple.com> wrote: >> On Wed, Jul 2, 2008 at 7:00 PM, Mike Stump <mrs at apple.com> wrote: >>> If we apply their logic to llvm, we can dominate, if we just target 8 >>> cores. :-) > > Does this mean llvm can not dominate if llvm target 1 core machine > also ? Making an optimizer/code generator

On Mar 12, 2008, at 12:49 PM, Mike Stump wrote: > No. Doh, you know, I was trying to find the quoted wording... What the big print giveth, the small print takes away. Ignore me... I was wrong.

Hi Piortr, This also breaks the hand-built VC++ project. Any clues on where I should define this? Thanks, snaroff -------------- next part -------------- A non-text attachment was scrubbed... Name: Picture 7.png Type: image/png Size: 13645 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090202/eb726ff5/attachment.png> -------------- next part

On Oct 14, 2008, at 5:41 PM, Chris Lattner wrote: > On Oct 14, 2008, at 4:30 PM, Mike Stump wrote: >> On Oct 14, 2008, at 1:54 PM, Eli Friedman wrote: >>> Maybe... although note that with gcc vector intrinsics, this >>> violates >>> strict aliasing. gcc does allow you to use a slightly more >>> elaborate >>> workaround with a union,

- Devang On May 9, 2008, at 5:03 PM, Mike Stump <mrs at apple.com> wrote: > > Ah, but you can use any intrinsic that is target independent.... The > gcc vector stuff is meant to work on all targets as I recall. Do you mean GCC has target independent vector intrinsics?

On Fri, May 9, 2008 at 8:42 PM, Devang Patel <dpatel at apple.com> wrote: > > > - > Devang > > On May 9, 2008, at 5:03 PM, Mike Stump <mrs at apple.com> wrote: >> >> Ah, but you can use any intrinsic that is target independent.... The >> gcc vector stuff is meant to work on all targets as I recall. > > Do you mean GCC has target independent