Displaying 20 results from an estimated 30000 matches similar to: "[LLVMdev] LLVM Logo"
2009 Jul 30
1
[LLVMdev] LLVM Logo
On Jul 30, 2009, at 1:33 AM, Bill Wendling wrote:
>>
>> That said, I'm not a graphic artist. I simply down-sampled the image
>> to get the "Small" one that I'd like to use on the sidebar. The
>> image
>> is complex enough that it will probably take someone who knows what
>> they are doing to make it look good. Any help is definitely
2013 May 25
2
[LLVMdev] [cfe-dev] [3.3 Release] Release Candidate 2 Available
On Fri, May 24, 2013 at 4:21 PM, Bill Wendling <wendling at apple.com> wrote:
> On May 24, 2013, at 1:19 PM, Bill Wendling <wendling at apple.com> wrote:
>
>> Hi!
>>
>> The binaries for the 3.3 release candidate 2 are starting to role in. Please take them and give them a go. Please file bug reports for any problems you encounter.
>>
>> At this point,
2013 May 24
0
[LLVMdev] [cfe-dev] [3.3 Release] Release Candidate 2 Available
On May 24, 2013, at 1:19 PM, Bill Wendling <wendling at apple.com> wrote:
> Hi!
>
> The binaries for the 3.3 release candidate 2 are starting to role in. Please take them and give them a go. Please file bug reports for any problems you encounter.
>
> At this point, we are taking fixes only for *serious* regressions from 3.2. I will be pushing back on all requests to merge
2010 Sep 15
0
[LLVMdev] Announcing: LLVM 2.8 Release Candidate 2 Tagging Tonight
On Wed, 15 Sep 2010 01:50:24 -0700
Bill Wendling <wendling at apple.com> wrote:
> On Sep 15, 2010, at 12:46 AM, Albert Graef wrote:
>
> > Bill Wendling wrote:
> >> Release testing of Release Candidate 1 is finished. I'll be tagging
> >> Release Candidate 2 tonight. If there are any fixes you want in,
> >> please get them approved as soon as
2009 Jul 30
0
[LLVMdev] LLVM Logo
On Jul 30, 2009, at 12:09 AM, Chris Lattner wrote:
> Hi All,
>
> I'm happy to announce that Apple has agreed to let llvm.org (and
> anyone else) use the great LLVM logo they designed for WWDC. If
> you're interested, you can see the full version of the logo on this
> page:
> http://llvm.org/Logo.html
>
> I personally think that this is a pretty great
2016 Mar 22
2
USB Drives with your Logo
Hi,
I wanted to follow up from last week. Did you receive the email I sent
you?
I am looking to reach the person that does your buying of branded
promotional products for your company?
Our company manufactures USB Flash Drives, printed with your logo, the
perfect marketing tool
for your business or organization.
We offer low minimum quantities, and all memory sizes.
We are always running a
2016 Mar 22
0
USB Drives with your Logo
I Apologize for all llvm-dev subscriber, it looks like this spam slipped in the middle this morning when I approved other (legitimate) emails to the list.
--
Mehdi
> On Mar 22, 2016, at 6:31 AM, Allison Green via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> Hi,
>
> I wanted to follow up from last week. Did you receive the email I sent
> you?
>
> I am
2015 Jan 05
2
[LLVMdev] LTO v. opt
Thanks to you both.
On my Linux (centos6) system, I have reproduce a variant of the bug and learned about
-plugin-opt=-debug-pass=Arguments
which I infer from comments is intended to built arguments to “opt” however I found that some of the arguments don’t seem to be quite correct. I assume this just minor bit rot.
bin/opt -o pass1.bc -datalayout -notti -basictti -x86tti -targetlibinfo
2016 Aug 24
0
[PATCH v2] drm/nouveau: add a LED driver for the NVIDIA logo
On 23/08/16 17:43, Emil Velikov wrote:
> On 23 August 2016 at 00:42, Martin Peres <martin.peres at free.fr> wrote:
>> v2:
>> - guard LED framework calls with ifdef CONFIG_LEDS_CLASS
>>
> IIRC kernel has the tendency of using static inlines in the headers
> when CONFIG_foo is not set. Worth using that and removing the ifdef
> from the source file ?
Oh, you
2015 Jan 05
2
[LLVMdev] LTO v. opt
On Jan 3, 2015, at 11:52 PM, Bill Wendling <isanbard at gmail.com> wrote:
> On Jan 2, 2015, at 8:32 PM, David Callahan <dcallahan at fb.com> wrote:
>
>> Hi,
>>
>> I am new to the LLVM dev community so forgive a perhaps obvious question. I am looking at bug 17623 which is an LTO/optimizer interaction bug. I am working on a Mac with Xcode installed but have
2009 Jul 30
10
[LLVMdev] LLVM Logo
Hi All,
I'm happy to announce that Apple has agreed to let llvm.org (and
anyone else) use the great LLVM logo they designed for WWDC. If
you're interested, you can see the full version of the logo on this
page:
http://llvm.org/Logo.html
I personally think that this is a pretty great logo/mascot for LLVM,
because it is very abstract, can be adapted in a variety of ways, is
2010 Sep 15
3
[LLVMdev] Announcing: LLVM 2.8 Release Candidate 2 Tagging Tonight
On Sep 15, 2010, at 12:46 AM, Albert Graef wrote:
> Bill Wendling wrote:
>> Release testing of Release Candidate 1 is finished. I'll be tagging
>> Release Candidate 2 tonight. If there are any fixes you want in, please
>> get them approved as soon as possible.
>
> Are there any tarballs for the release candidates available? Tanya used
> to make these available
2003 Mar 31
0
Booting Linux off a CF card
Hello,
I am not sure if I am posting this question in the right place, so please
forgive me if this is an error :)
I am completely new to using Linux off a flash card, but I need to do it as
a project for my office. We have an 8MB CF card, which is connected to my
Linux box via an IDE adapter. I need to somehow make the system boot off
the CF card and give me a shell prompt.
I have managed to
2006 May 16
2
Polycom 501 logo onscreen
Anyone know how (or if it's possible) to get a logo on the screen of
a Polycom 501?
I've been looking around for hints on how to do it but so far nothing
would indicate Polycom supports doing it.
-bill
2006 Dec 14
1
[LLVMdev] MachineFunction.cpp!!!
Did someone make a change in MachineFunction and forget to update something?
g++ -I/Volumes/data/Wendling/llvm-submission/build/obj/obj-llvm/lib/CodeGen
-I/Volumes/data/Wendling/llvm-submission/build/obj/src/llvm/lib/CodeGen
-I/Volumes/data/Wendling/llvm-submission/build/obj/obj-llvm/include
-I/Volumes/data/Wendling/llvm-submission/build/obj/src/llvm/include
2011 Nov 08
4
[LLVMdev] [cfe-dev] LLVM 3.0rc3 Testing Beginning
On Nov 8, 2011, at 7:18 AM, Jay Foad wrote:
> On 7 November 2011 22:00, Bill Wendling <wendling at apple.com> wrote:
>> We are starting on our third (and hopefully last) round of testing for LLVM 3.0. Please visit:
>>
>> http://llvm.org/pre-releases/3.0/rc3/
>>
>> for the sources. There are also binaries for Darwin up there, with more to come during
2011 Nov 08
0
[LLVMdev] [cfe-dev] LLVM 3.0rc3 Testing Beginning
Which files are needed to build clang? Is it clang-3.0rc2 and llvm-3.0rc3 or do I need the whole test suite?
John
Dr John P. Fletcher Tel: (44) 121 204 3389 (direct line), FAX: (44) 121 204 3678
Chemical Engineering and Applied Chemistry (CEAC),
Associate Dean - External Relations,
School of Engineering and Applied Science (EAS),
Aston University, Aston Triangle, BIRMINGHAM B4 7ET
2014 Aug 25
2
[LLVMdev] [cfe-dev] [3.5 Release] Release Candidate 3 Now Available
The ARM binaries seem to be corrupt. Although correctly signed, the xz file seems to be truncated
arm7% unxz < clang+llvm-3.5.0-rc3-armv7a-linux-gnueabihf.tar.xz | wc -c
unxz: (stdin): Unexpected end of input
133214381
M.E.O.
On Aug 21, 2014, at 10:56 AM, Bill Wendling <isanbard at gmail.com> wrote:
> Ahem. And now for the correct URL:
>
>
2012 Jul 11
4
[Bug 2025] New: Comments with 1024 chars or more break sshd_config
https://bugzilla.mindrot.org/show_bug.cgi?id=2025
Priority: P5
Bug ID: 2025
Assignee: unassigned-bugs at mindrot.org
Summary: Comments with 1024 chars or more break sshd_config
Severity: normal
Classification: Unclassified
OS: Linux
Reporter: bugzilla.mindrot.org-mail at nils.toedtmann.net
Hardware: All
2013 Apr 03
3
[LLVMdev] [Announcement] 3.3 Release Planning!
On Apr 3, 2013, at 2:07 AM, Renato Golin <renato.golin at linaro.org> wrote:
> On 1 April 2013 22:05, Bill Wendling <wendling at apple.com> wrote:
> We would like to support ARM again.
>
> Hi Bill,
>
> Glad you asked! ;)
>
> I'm getting the test-suite bot green (a few minor tweaks and we're good) and that should get us well ahead of what we've