search for: sectionnames

...ew minutes ago, I left off the rewritten read.ssd(). I've included it at the end this time. read.ssd() invokes PROC COPY to create an xport file, but PROC COPY has some annoying limitations that read.ssd() should deal with. The first is that PROC COPY doesn't work with member names (the sectionnames argument to read.ssd) longer than 8 characters. The second is that PROC COPY also fails if any of the columns in the dataset being copied are too long, unless you first set (in SAS) "option validvarname = v6;". I'm including here a rewritten read.ssd() that deals with these two is...

Dear all, I want to start my post by expressing my sincere gratitude for all the help this group has given me in Sweave/Latex/R. The tools are excellent and so is the community! On to the question. My Sweave code is intended to make lots of plots and create a *.pdf document. Sweave is perfect for this. The only problem is that I find myself using the same R code, within my Sweave input file

Hi! I need to import in R some SAS dataset (sas7bdat). I found two functions to do it: "read.ssd" from the package "foreign" and "sas.get" from "Hmisc". df = read.ssd(libname = path2data, sectionnames = "sasSmallDataset", tmpXport = path2data, tmpProgLoc = path2data, sascmd = path2sas) sas.get(libraryName = path2data, member = "sasSmallDataset", formats = FALSE, sasprog = path2sas, keep.log = TRUE) where path2data is the directory on which is contained the file sas, sasSmall...

I recently examined a bug in a program, and it turned out that the customer was using the section attribute as a form of inline-assembly mechanism, with something like: __attribute__((section("sectionName\nasm\nasm\nasm"))) this was really ugly and not at all obvious where the problem originated. Is there any way of getting LLVM or CLang to validate the name used in the section

Hi, Thanks for pointing direction. As far, as I understand by reversing, logic, that I want to overwrite is digged into: lib/MC/MCSectionELF.cpp MCSectionELF::PrintSwitchToSection if (ShouldOmitSectionDirective(SectionName, MAI)) { OS << '\t' << getSectionName() << '\n'; return; } // otherwise print ".section" directive and then section

Hi Shankar, On Tue, Feb 12, 2013 at 10:46 PM, Shankar Easwaran <shankare at codeaurora.org> wrote: > Author: shankare > Date: Tue Feb 12 12:46:53 2013 > New Revision: 174990 > > URL: http://llvm.org/viewvc/llvm-project?rev=174990&view=rev [...] > ELFDefinedAtom<ELFT> *createDefinedAtomAndAssignRelocations( > StringRef symbolName, StringRef

Hi, Thanks for the explanation. If I understand you properly you suggest to move relocation parsing to the class with the following interface. Right? Who will be user of this class? If it is still only ELFFile class, what benefits will we get from separation of this logic? template <class ELFT> class ELFRelocationReader { public: ELFRelocationReader(.....); // Returns all created

On Thu, Mar 15, 2012 at 11:00:54AM +0400, Konstantin Vladimirov wrote: > Hi, > > Thanks for pointing direction. As far, as I understand by reversing, > logic, that I want to overwrite is digged into: > > lib/MC/MCSectionELF.cpp > > MCSectionELF::PrintSwitchToSection > > if (ShouldOmitSectionDirective(SectionName, MAI)) { > OS << '\t'

Hi, all, Please tell me about the patch and description below. https://github.com/dovecot/core/commit/5f46b863383fc94afcd2693ecae8788cb5fdd20c example-config: Use a default uncommented "namespace inbox". https://doc.dovecot.org/configuration_manual/namespace/ There's a default inbox namespace added in 10-mail.conf. If the configuration doesn't explicitly specify a

Full_Name: Jeff Hallman Version: 2.4.1 OS: Linux Submission from: (NULL) (132.200.32.34) read.ssd() invokes PROC COPY to create an xport file, but PROC COPY has some annoying limitations that read.ssd() should deal with. The first is that PROC COPY doesn't work with member names (the sectionnames argument to read.ssd) longer than 8 characters. The second is that PROC COPY also fails if any of the columns in the dataset being copied are too long, unless you first set (in SAS) "option validvarname = v6;". I'm including here a rewritten read.ssd() that deals with these two is...

...of the “foreign” package, but I get an error message “SAS failed”. I believe I have specified the paths correctly (after reading some previous posts I made sure that I do it right). Below is the small code: sashome<- "C:/Program Files/SAS/SAS 9.1" read.ssd(libname="R:/", sectionnames="test", sascmd=file.path(sashome, "sas.exe")) Please let me know where I am making the mistake. Is it because of the size of the file or the location of the file (in server instead of local hard drive)? Thanks in advance, Santanu -- ------------------------------------...

Hi all, Ok, up until now, I've only always allowed IMAPS connections to dovecot on port 993. I want to also start allowing clients to user port143+STARTTLS, but I walso want to make sure both ports are locked down to ONLY allow secure connections. So... is disable_plaintext_auth = yes in the main config enough to accomplish this? http://wiki2.dovecot.org/SSL/DovecotConfiguration says:

Would it be useful for Clang to warn about section names with unusual characters? -Hal ----- Original Message ----- > From: "Reid Kleckner via llvm-dev" <llvm-dev at lists.llvm.org> > To: "Martin J. O'Riordan" <martin.oriordan at movidius.com> > Cc: "LLVM Developers" <llvm-dev at lists.llvm.org> > Sent: Wednesday, October 5, 2016

Hi Michael, Overall patch looks good. I do have a few comments below. My main comment is please try to make the style match that used in the MCMachOStreamer more closely. I intend to refactor more functionality into the base MCObjectStreamer class, and having them use consistent idioms makes this easier; specific instances are included in the comments: -- > diff --git

I am attempting to read in a SAS 9.1 data file. After starting R I change to the directory containing the sas data file and use the "dir" command to confirm that it is there. Then I run the following R-code: library(foreign) sashome <- "/Program Files/SAS/SAS 9.1" test<-read.ssd(file.path(sashome), "pcb", sascmd = file.path(sashome,

On Sun, Jul 11, 2010 at 6:10 PM, Chris Lattner <clattner at apple.com> wrote: > This probably needs to be slightly tweaked to work with mainline.  I don't see anything objectionable, but I think Daniel needs to review this one. Updated patch to work with mainline. http://github.com/Bigcheese/llvm-mirror/commit/d19a4c82c18afc4830c09b70f02d162292231c94 - Michael Spencer

Hi Shankar, I almost implement ELFRelocationReader but still not completely sure that this is a right direction. Suppose somebody wants to override creation of the `ELFReference` object from the `Elf_Rela` or `Elf_Rel` record. Let's consider two implementations A and B: A: ===== 1. Factor out `ELFReference` creation from `createDefinedAtomAndAssignRelocations` into a couple of virtual

Hi Folks, I have a question regarding LLD support for ld64 mach-o linker synthesised symbols. I did a quick search of the LLD source and I can not find support for them so before I start trying to use lld I thought I would ask. I have found a couple of cases where they are essential. i.e. where there is no other way to get the required information, such as getting the address of the mach-o

Hi, In the document: http://llvm.org/docs/WritingAnLLVMBackend.html described example like: SparcTargetAsmInfo::SparcTargetAsmInfo(const SparcTargetMachine &TM) { Data16bitsDirective = "\t.half\t"; Data32bitsDirective = "\t.word\t"; Data64bitsDirective = 0; // .xword is only supported by V9. ZeroDirective = "\t.skip\t"; CommentString = "!";

Hello > I really need in my backend value for this section, distinct from > default. Where can I set it? It was renamed to ReadOnlySection. You might want to check the logic inside CodeGen/TargetLoweringObjectFileImp.cpp (in particular - TargetLoweringObjectFile::SelectionSectionForGlobal) to see how it's used. -- With best regards, Anton Korobeynikov Faculty of Mathematics and