similar to: [klibc:master] [OUTPUT] Make outc an inline function

Commit-ID: e4610e5e04a3292a48a239be366e7767b64ffdcb Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=e4610e5e04a3292a48a239be366e7767b64ffdcb Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Mon, 27 Oct 2014 12:19:25 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 25 Jan 2019 02:57:21 +0000 [klibc] [BUILTIN] Handle

Commit-ID: 27d0e9f3b74b25e5d2c9f366074edb77b9ef5f9f Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=27d0e9f3b74b25e5d2c9f366074edb77b9ef5f9f Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Mon, 27 Oct 2014 12:19:25 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:54 +0000 [klibc] dash: [BUILTIN]

Commit-ID: a61f802e418cd4cf282ccdb60229335e0c09f3bf Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=a61f802e418cd4cf282ccdb60229335e0c09f3bf Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Mon, 5 Jan 2015 22:42:32 +1100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 25 Jan 2019 02:57:21 +0000 [klibc] input: Move all input

Commit-ID: 7976a4e8b6d3adc72d9a07f37a8f470f7345c6db Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=7976a4e8b6d3adc72d9a07f37a8f470f7345c6db Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Mon, 5 Jan 2015 22:42:32 +1100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:54 +0000 [klibc] dash: input: Move all

Commit-ID: 39d9f472762cd928024a5cb836aef46f14031756 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=39d9f472762cd928024a5cb836aef46f14031756 Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Mon, 5 Jan 2015 22:50:57 +1100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 25 Jan 2019 02:57:21 +0000 [klibc] input: Allow two

Commit-ID: 21178cb4e427385a4aba8dc2a2df50f34ae6684e Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=21178cb4e427385a4aba8dc2a2df50f34ae6684e Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Mon, 5 Jan 2015 22:50:57 +1100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:54 +0000 [klibc] dash: input: Allow two

Commit-ID: 31ef3f49d4fd96b67b0e578c5f672fe428430b14 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=31ef3f49d4fd96b67b0e578c5f672fe428430b14 Author: Antonio Ospite <ao2 at ao2.it> AuthorDate: Sat, 15 Dec 2018 18:49:32 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 16:20:40 +0000 [klibc] dash: output: Fix clang warnings

- Convert the "old style" GNU field designator extension to the new style. - Use proper indexing into a string literal. - Use "%s" for the format string in "fmtstr". - Add or remove casts of the "void *" argument of ioctl. - Convert "if (!exitstatus == isor)" to "if ((!exitstatus) == isor)" which retains the current semantics, but may

I'm trying to figure out why the presence of a Fortran call affects the result of a floating-point operation. I have C functions void test1(int *n, double *f){ int outC; double c0; c0 = (double) *n * *f; outC = floor(c0); printf("when f computed by R, C says %d by itself\n",outC); } void test2(int *n, double *f){ extern int F77_NAME(ifloor)(double *); int

Commit-ID: 3bfbb8db1389fde819e28273b8e85262e58a9a1b Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=3bfbb8db1389fde819e28273b8e85262e58a9a1b Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Mon, 27 Oct 2014 15:42:23 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 25 Jan 2019 02:57:21 +0000 [klibc] [OUTPUT] Add likely

Commit-ID: 47458a252e45651bcf39282172ee688073234959 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=47458a252e45651bcf39282172ee688073234959 Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Mon, 27 Oct 2014 15:42:23 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:54 +0000 [klibc] dash: [OUTPUT] Add

Hi all, I have a question with the "getelemptr" instruction. E.g.: I have some GEP instructions in my program. Some look like: <INST_GEP op0=26 op1=64 op2=429/> . <INST_GEP op0=341 op1=64 op2=101 op3=499 op4=0/> The first instruction above in assembly file: %tmp60 = getelementptr [512 x i32]* @weights, i32 0, i32 %k.3.ph Ok, we see it all: Index of @weights in value

Commit-ID: f835bc21ece0ec55824bd7538e4c2a04489812ef Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=f835bc21ece0ec55824bd7538e4c2a04489812ef Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Mon, 27 Oct 2014 16:23:33 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 25 Jan 2019 02:57:21 +0000 [klibc] [BUILTIN] Simplify

Commit-ID: 1fb4949c5a40f0bb6da7993a2ab034ec3b39477d Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=1fb4949c5a40f0bb6da7993a2ab034ec3b39477d Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Mon, 27 Oct 2014 16:23:33 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:54 +0000 [klibc] dash: [BUILTIN]

This release continues to stabilise the stdio codebase. It has fixes for latest linux 3.6, a sync to latest dash and of course several arm fixes. Thank you all. Bill Pringlemeir (1): [klibc] [PATCH] fix ARM longjmp with zero 'val'. Christoph Mathys (1): [klibc] [BUILTIN] Add support for ulimit -r Colin Watson (1): [klibc] include: [sys/time.h] fix for Linux 3.5.1

Commit-ID: 166a88f4568067378ddce23b91be7b4ec9a9dfb4 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=166a88f4568067378ddce23b91be7b4ec9a9dfb4 Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Sat, 19 May 2018 02:39:52 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:55 +0000 [klibc] dash: eval: Add

On 11/30/2012 6:36 PM, Lang Hames wrote: > > > RBP is used as the frame pointer on x86 (hence its automatic > appearance in your code), and shouldn't be allocated to any vreg in > function bar. Loading/saving RBP should be managed by the stack frame > setup/teardown code. > If it doesn't already, your allocator should filter out reserved > registers (See

This is a series of patches for clang compatibility: - Using flags needed flags and removing unsupported flags. - Adding support for clang's LLD linker. - Removing a variety of warnings. Bill Wendling (3): [klibc] Kbuild: use "libc.a" with clang [klibc] Kbuild: Add "-fcommon" for clang builds [klibc] Clean up clang warnings Michael Davidson (1): [klibc] Kbuild:

Hello, I have a loop with 1000 repetitions which includes OR computation of an exposure factor and outcome. I compute OR like this: t<-table(exposure,outcome) oddsratio(t)$measure["estimate"] This gives me the estimates for exposure=0 and exposure=1 but exposure=0 is the reference group and i need only the estimate for exposure=1. I specified a matrix OR with 3 columns (for OR

Hi, Could someone help with coding this in R? I need to select one row per patient i in clinic j. The data is organized similar to that shown below. Two columns - patient i in column j identify each unique patient. There are two columns on outcome. Some patients have multiple rows with each row representing one visit, coded for in the column, visit. Some patients have just one row indicating