similar to: [LLVMdev] printing hex format for floating point number

Here's a patch that contains Hexagon Test cases. Please review. Sirish -- Qualcomm Innovation Center, Inc is a member of Code Aurora Forum -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: HexagonTestCases.patch URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120420/eb32dede/attachment.ksh>

Hi, Here's a patch for Hexagon Packetizer for review. This patch does not yield any warnings. Sirish -- Qualcomm Innovation Center, Inc is a member of Code Aurora Forum -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: HexagonPacketizer.patch URL:

On Apr 20, 2012, at 1:58 PM, Sirish Pande <spande at codeaurora.org> wrote: > Here's a patch that contains Hexagon Test cases. Please review. You can't include these in the patches that they're supposed to go along with? -eric

No test cases for a 500k patch? -eric On Apr 18, 2012, at 9:18 PM, Sirish Pande wrote: > Hi, > > Here's a patch for Hexagon Packetizer for review. This patch does not yield any warnings. > > Sirish > > -- > Qualcomm Innovation Center, Inc is a member of Code Aurora Forum > > <HexagonPacketizer.patch>_______________________________________________

On Sep 20, 2012, at 3:01 AM, Dmitri Gribenko <gribozavr at gmail.com> wrote: > On Wed, Sep 19, 2012 at 3:00 AM, Martinez, Javier E > <javier.e.martinez at intel.com> wrote: >> We have identified functions in LLVM sources using a static code analyzer >> which are marked as a “security vulnerability”[1][2]. There has been work >> already done to address some of

Sure I can do that. In that case, let me recreate all the patches (along with the test cases) and put up the patches for review. sirish On 4/20/2012 4:16 PM, Eric Christopher wrote: > On Apr 20, 2012, at 1:58 PM, Sirish Pande<spande at codeaurora.org> wrote: > >> Here's a patch that contains Hexagon Test cases. Please review. > You can't include these in the

On Wed, Sep 19, 2012 at 3:00 AM, Martinez, Javier E <javier.e.martinez at intel.com> wrote: > We have identified functions in LLVM sources using a static code analyzer > which are marked as a “security vulnerability”[1][2]. There has been work > already done to address some of them for Linux (e.g. snprintf). We are > attempting to solve this issue in a comprehensive fashion

On Thu, Sep 20, 2012 at 10:13 AM, Chris Lattner <clattner at apple.com> wrote: > > On Sep 20, 2012, at 3:01 AM, Dmitri Gribenko <gribozavr at gmail.com> wrote: > > > On Wed, Sep 19, 2012 at 3:00 AM, Martinez, Javier E > > <javier.e.martinez at intel.com> wrote: > >> We have identified functions in LLVM sources using a static code > analyzer >

> I’ll prepare a patch that replaces the string manipulation functions an > appropriate string object. Please break the patch up into focused chunks, one per logical change. We try to keep all LLVM development as incremental as possible [1]. I recommend fixing a single logical occurrence (such as fixing APFloat::convertToHexString()) and then mailing the patch to llvm-commits. It's

Hi, Given the following in ISDOpcodes.h SETO, // 0 1 1 1 True if ordered (no nans) SETUO, // 1 0 0 0 True if unordered: isnan(X) | isnan(Y) Is it safe to assume that SETO is not of SETUO? We have support for setuo in the architecture but not seto. Sirish -------------- next part -------------- An HTML attachment was scrubbed...

Hi, Look at the following code: Look at the following C code seqence: unsigned char mainGtU ( unsigned int i1, unsigned int i2, unsigned char* block) { unsigned char c1, c2; c1 = block[i1]; c2 = block[i2]; if (c1 != c2) return (c1 > c2); i1++; i2++; c1 = block[i1]; c2 = block[i2]; if (c1 != c2) return (c1 > c2); i1++; i2++; .. ..

Hi, Here's a Hexagon patch for replacing transfer/copy instructions to combine for review. This patch does not yield any warnings on Hexagon, Arm and X86 build on Linux. This work is by Arnold Schwaighofer. Sirish -- Qualcomm Innovation Center, Inc is a member of Code Aurora Forum -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name:

On Fri, May 19, 2017 at 4:32 PM, Daniel Berlin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > i think you'd have to write some idiom recognizer here. The ones we have > won't do it. > > I guess my other question would be how commonly this happens. If it's common > and matters a lot, awesome. > I wouldn't do it just to fix SPEC :P > > (people who

>From the responses it's pretty clear that the preference is to avoid using C string functions altogether. I've attached at list of calls in Clang/LLVM. The EASY/MEDIUM/DIFFICULT tag is an estimate of the effort to replace the call based on the location of the source buffer. If there are no objections I'll prepare a patch that replaces the string manipulation functions an

On Mon, 4 Jun 2012 11:41:43 -0500 Sebastian Pop <spop at codeaurora.org> wrote: > On Mon, Jun 4, 2012 at 11:22 AM, Sebastian Pop <spop at codeaurora.org> > wrote: > >> Why don't you call it with "Promote" instead of > >> "Custom" and let the Legalizer do the job? Does it not work? > > > > I tried this, and the legalizer will

is there a snappy way to get hex codes to render as html special chars? ie. method(''k%FClschrank'') returns ''k&uuml;lschrank'' thanks bryce -- Posted via http://www.ruby-forum.com/.

This is a multipart MIME message. --= Multipart Boundary 1009021339 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit Hello there Did you know that you can program smart cards with files from the internet and open lots of pay per view chanells for your televisual pleasure. Take a look at http://MagicFun.da.ru for the latest hex files. Many thanks Jay.

Hello there Did you know that you can program smart cards with files from the internet and open lots of pay per view chanells for your televisual pleasure. Take a look at http://MagicFun.da.ru for the latest hex files. Many thanks Jay. -------------- next part -------------- HTML attachment scrubbed and removed

http://defect.opensolaris.org/bz/show_bug.cgi?id=1053 Summary: ''zfs create'' core dumped with keysource=hex,prompt and unmatched entered in Classification: Development Product: zfs-crypto Version: unspecified Platform: Other OS/Version: Solaris Status: NEW Severity: normal

Hello world: Has anyone used hex notation within R to represents integers? Cheers, Steve Vejcik