search for: ffoo

...code generation. - Not convinced here of the facility to do so. Could just recompile the individual bitcode files to get what you want, but there are some users that are trying to ship bitcode (as crazy as that sounds). 2) How to pass other sorts of options to the backend for code generation - -ffoo options -fno-foo options. I.e. -fno-inline, etc. I think this is really pretty important from the user POV. It affects things at a more global level. 3) The llvm developer debugging story - It's useful for llvm developers to be able to more accurately debug a set of IR using bisection or bein...

...e) for the column headers, and then "deeper down" C code which I did not investigate. But just looking a bit at such a file() object with writeLines() seems slightly revealing, as e.g., 'eol' does not seem to "work" for this encoding: > fn <- tempfile("ffoo"); ff <- file(fn, open="w", encoding = "UTF-16LE") > writeLines(LETTERS[3:1], ff); writeLines("|", ff); writeLines(">a", ff) > close(ff) > file.show(fn) CBA|> > file.size(fn) [1] 5 > >> The...

...-length input */ > } else > > >> >> But just looking a bit at such a file() object with writeLines() >> seems slightly revealing, as e.g., 'eol' does not seem to >> "work" for this encoding: >> >> > fn <- tempfile("ffoo"); ff <- file(fn, open="w", encoding = "UTF-16LE") >> > writeLines(LETTERS[3:1], ff); writeLines("|", ff); writeLines(">a", ff) >> > close(ff) >> > file.show(fn) >> CBA|> >> > fi...

...-length input */ > } else > > >> >> But just looking a bit at such a file() object with writeLines() >> seems slightly revealing, as e.g., 'eol' does not seem to >> "work" for this encoding: >> >> > fn <- tempfile("ffoo"); ff <- file(fn, open="w", encoding = "UTF-16LE") >> > writeLines(LETTERS[3:1], ff); writeLines("|", ff); writeLines(">a", ff) >> > close(ff) >> > file.show(fn) >> CBA|> >> > file.si...

...input */ > } else > > > > > > But just looking a bit at such a file() object with writeLines() > > seems slightly revealing, as e.g., 'eol' does not seem to > > "work" for this encoding: > > > > > fn <- tempfile("ffoo"); ff <- file(fn, open="w", encoding = "UTF-16LE") > > > writeLines(LETTERS[3:1], ff); writeLines("|", ff); writeLines(">a", ff) > > > close(ff) > > > file.show(fn) > > CBA|> > > > fi...

...>>> >>>> But just looking a bit at such a file() object with writeLines() >>>> seems slightly revealing, as e.g., 'eol' does not seem to >>>> "work" for this encoding: >>>> >>>> > fn <- tempfile("ffoo"); ff <- file(fn, open="w", encoding = >>>> "UTF-16LE") >>>> > writeLines(LETTERS[3:1], ff); writeLines("|", ff); >>>> writeLines(">a", ff) >>>> > close(ff) >>>> &g...

...;>>> >>>> But just looking a bit at such a file() object with writeLines() >>>> seems slightly revealing, as e.g., 'eol' does not seem to >>>> "work" for this encoding: >>>> >>>> > fn <- tempfile("ffoo"); ff <- file(fn, open="w", encoding = "UTF-16LE") >>>> > writeLines(LETTERS[3:1], ff); writeLines("|", ff); writeLines(">a", ff) >>>> > close(ff) >>>> > file.show(fn) >>>>...

...se >> >> >>> >>> But just looking a bit at such a file() object with writeLines() >>> seems slightly revealing, as e.g., 'eol' does not seem to >>> "work" for this encoding: >>> >>> > fn <- tempfile("ffoo"); ff <- file(fn, open="w", encoding = >>> "UTF-16LE") >>> > writeLines(LETTERS[3:1], ff); writeLines("|", ff); >>> writeLines(">a", ff) >>> > close(ff) >>> > file.show(fn) >&g...

...e iconv signal -1 on zero-length input */ } else > > But just looking a bit at such a file() object with writeLines() > seems slightly revealing, as e.g., 'eol' does not seem to > "work" for this encoding: > > > fn <- tempfile("ffoo"); ff <- file(fn, open="w", encoding = "UTF-16LE") > > writeLines(LETTERS[3:1], ff); writeLines("|", ff); writeLines(">a", ff) > > close(ff) > > file.show(fn) > CBA|> > > file.size(fn) > [1]...

...d besides: the frontend needs to know the backend in order to conform to the ABI, set macros, emit calls to target-specific intrinsics, etc. I'll send a review of r233227 in a moment to that effect ;). > 2) How to pass other sorts of options to the backend for code generation > > - -ffoo options -fno-foo options. I.e. -fno-inline, etc. I think this is really pretty important from the user POV. It affects things at a more global level. This is easy to solve for -fno-inline in particular: we should just add a function attribute (`noinline`?) that the inliner should treat as a synony...

...>>> But just looking a bit at such a file() object with writeLines() >>>>> seems slightly revealing, as e.g., 'eol' does not seem to >>>>> "work" for this encoding: >>>>> >>>>> > fn <- tempfile("ffoo"); ff <- file(fn, open="w", encoding = >>>>> "UTF-16LE") >>>>> > writeLines(LETTERS[3:1], ff); writeLines("|", ff); >>>>> writeLines(">a", ff) >>>>> > close(ff) >&gt...

...lse >> >> >>> >>> But just looking a bit at such a file() object with writeLines() >>> seems slightly revealing, as e.g., 'eol' does not seem to >>> "work" for this encoding: >>> >>> > fn <- tempfile("ffoo"); ff <- file(fn, open="w", encoding = "UTF-16LE") >>> > writeLines(LETTERS[3:1], ff); writeLines("|", ff); writeLines(">a", ff) >>> > close(ff) >>> > file.show(fn) >>> CBA|> >>&...

If I execute the code from the "?write.table" examples section x <- data.frame(a = I("a \" quote"), b = pi) # (ommited code) write.csv(x, file = "foo.csv", fileEncoding = "UTF-16LE") the resulting CSV file has a size of 6 bytes which is too short (truncated): """,3 The problem seems to be the iconv function: