Displaying 9 results from an estimated 9 matches for "lifeblood".
2015 Feb 25
2
[LLVMdev] RFC: PerfGuide for frontend authors
...n, so I would like this document to be in a directory
> docs/FrontendInfo/ or something like that (bikeshed) so that we can
> easily split out into new docs as needed for some breathing room, or
> to give some structure for readers to follow.
>
> Our optimizer and backends are our lifeblood, but frontends are our
> reason for existence. This kind of frontend-oriented documentation has
> been needed for a long time. Thanks for kicking it off!
>
> -- Sean Silva
>
> On Mon, Feb 23, 2015 at 4:46 PM, Philip Reames
> <listmail at philipreames.com <mailto:listma...
2005 May 18
3
Installing CentOS on RAID PATA not SATA - A8V
I'm trying to install CentOS 4 on an A8V on the
PATA/Raid drives on the Promise controller. The
Promise controller is recognized (sata_promise), but
the PATA drives are not recognized. Base on this
thread
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=147303
it seems that there is a patch which was merged in
2.6.11 to get pata working.
Any ideas how to proceed?
Thanks in advance
2019 Nov 08
2
Enable Contributions Through Pull-request For LLVM
I'm not sure the idea that enabling pull requests will make it easier
for new contributors is fully thought out. Just because more people
might be familiar with GitHub, doesn't mean it is superior. I've found
the workflow on Phabricator to be really easy. I think many people
agree that Phabricator is really good, I don't think we would want to
get rid of Phabricator and while its
2019 Nov 12
4
Enable Contributions Through Pull-request For LLVM
...> largely standardized; you might design a superior set of controls,
> but the simple fact of being different from all the others would be
> a barrier to adoption. Even if GitHub's workflow is flawed, it is
> what new contributors will be used to, and new contributors are the
> lifeblood of the project. And as a major project hosted on GitHub,
> it is not impossible that we could influence GitHub to smooth it out
> to better suit our use-cases.
>
> Or, check out Hal Finkel's suggestion, which would allow casual
> contributors to at least start out with their accu...
2008 Oct 01
1
"dovecot: Maximum number of mail processes exceeded"
....conf
--
Ralf Hildebrandt (Ralf.Hildebrandt at charite.de) snickebo at charite.de
Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155
http://www.arschkrebs.de I'm looking for a job
Vampireware /n/, a project, capable of sucking the lifeblood out of
anyone unfortunate enough to be assigned to it, which never actually
sees the light of day, but nonetheless refuses to die.
2015 Feb 24
9
[LLVMdev] RFC: PerfGuide for frontend authors
I'd like to propose that we create a new Performance Guide document.
The target of this document will be frontend authors, not necessarily
LLVM contributors. The content will be a collection of items a frontend
author might want to know about how to generate LLVM IR which will
optimize well.
Some ideas on topics that might be worthwhile:
- Prefer sext over zext when value is known to be
2009 Jun 09
2
Comparing R and SAs
Hi:
For those of you who are adept at both SAS and R, I have the following questions:
a) What are some reasons / tasks for which you would use R over SAS and vice versa?
b) What are some things for which R is a must have that SAS cannot fulfill the requirements?
I am on the ramp up on both of them. The general feeling that I am getting by following this group is that R updates to the product are
2020 Jan 30
4
(SOLVED) YUM (DNF) Possible Confusion Centos 8
On 1/24/20 8:02 AM, Simon Matter via CentOS wrote:
>> <lots snipped>
>>
>>
>>> The redhat access page comes up in both google and duckduckgo when I put
>>> in the entire 4 lines of the error message.? You still have to login to
>>> see the solution.
>>>
>>>
2014 Oct 31
0
asterisk-users Digest, Vol 123, Issue 38
...nduct
> >
> > You have repeatedly insulted members of the Asterisk community using
> > derogatory language that is inappropriate for this mailing list. This
> > creates a hostile atmosphere that makes it difficult for productive
> > communication to occur, which is the lifeblood of this open source
> > project. Members of an open source community should not feel like they
> > are under attack merely for expressing an opinion. While we value the
> > opinions you bring to the discussion, your tone and choice of language
> > is completely inappropriate...