search for: xcu

Displaying 11 results from an estimated 11 matches for "xcu".

Did you mean: xcs
2012 Sep 10
3
[LLVMdev] Question about ctors, dtors and sections on Windows
...o all! I extended the LDC2 with a pragma to register a funcion in the llvm.global_ctors or llvm.global_dtors list. On Linux, references to these functions are placed in .ctors and .dtors sections and everything runs fine. On Windows, functions from llvm.global_ctors are placed in section .CRT$XCU, which is automatically called by the MS C Runtime. However, functions from llvm.global_dtors are placed in section .dtors which is unknown to the runtime. Therefore only ctors are called. Is this expected behaviour? My expectation was that the dtors placed in .CRT$XTU which are the C terminat...
2013 Sep 03
2
[LLVMdev] Proposal: Adding an optional association field to llvm.global_ctors
...ion >> with this >> attribute is only linked if the associated section is chosen for the >> final link. >> Otherwise it is discarded. >> >> In this way, only one initializer is linked and only one entry is >> produced in >> the initializer array (.CRT$XCU). Everyone I've spoken with so far thinks >> this >> is basically awesome and is much cleaner than using guard variables. :) >> >> I propose changing LangRef to make llvm.global_ctors and >> llvm.global_dtors be >> arrays of { i32, void()*, i8* }, where the l...
2013 Sep 04
0
[LLVMdev] Proposal: Adding an optional association field to llvm.global_ctors
...is > attribute is only linked if the associated section is chosen for the > final link. > Otherwise it is discarded. > > In this way, only one initializer is linked and only one entry is > produced in > the initializer array (.CRT$XCU). Everyone I've spoken with so far > thinks this > is basically awesome and is much cleaner than using guard variables. :) > > I propose changing LangRef to make llvm.global_ctors and > llvm.global_dtors be > arrays of { i32, void()*, i8...
2012 Sep 10
0
[LLVMdev] Question about ctors, dtors and sections on Windows
Hello > On Windows, functions from llvm.global_ctors are placed in section .CRT$XCU, > which is automatically called by the MS C Runtime. Only if you link with MS runtime. Mingw follows standard .ctors / .dtors scheme. > My expectation was that the dtors placed in .CRT$XTU which are the C > terminator functions. Maybe there is a way to customize this? Yes. Target (or,rat...
2013 Aug 26
2
[LLVMdev] Proposal: Adding an optional association field to llvm.global_ctors
...called IMAGE_COMDAT_SELECT_ASSOCIATIVE. The semantics are that the section with this attribute is only linked if the associated section is chosen for the final link. Otherwise it is discarded. In this way, only one initializer is linked and only one entry is produced in the initializer array (.CRT$XCU). Everyone I've spoken with so far thinks this is basically awesome and is much cleaner than using guard variables. :) I propose changing LangRef to make llvm.global_ctors and llvm.global_dtors be arrays of { i32, void()*, i8* }, where the last field is an optional pointer to a GlobalValue. Ol...
2006 Jan 20
1
Bug: Copying several files to non-directory.
...a b b Ouch! Also, for comparison: $ cp a b c cp: copying multiple files, but last argument `c' is not a directory Try `cp --help' for more information. $ rcp a b c rcp: c: Not a directory. $ Note that the cp behavior is specified in SuSv2. (http://www.opengroup.org/onlinepubs/007908799/xcu/cp.html, "Second synopsis") Also, and this might be a separate bug, note how openssh exits with return code of 1. This was verified using various versions of scp from 3.6.1p2 to 4.2, on linux (various versions) and openbsd. /August. -- Bj?rn Augustsson Sysadmin IT Systems &a...
2013 Sep 02
0
[LLVMdev] Proposal: Adding an optional association field to llvm.global_ctors
...CT_ASSOCIATIVE. The semantics are that the section with this > attribute is only linked if the associated section is chosen for the final link. > Otherwise it is discarded. > > In this way, only one initializer is linked and only one entry is produced in > the initializer array (.CRT$XCU). Everyone I've spoken with so far thinks this > is basically awesome and is much cleaner than using guard variables. :) > > I propose changing LangRef to make llvm.global_ctors and llvm.global_dtors be > arrays of { i32, void()*, i8* }, where the last field is an optional pointer t...
2015 Sep 23
10
[Bug 2471] New: "match exec" prepends "exec" to its command
https://bugzilla.mindrot.org/show_bug.cgi?id=2471 Bug ID: 2471 Summary: "match exec" prepends "exec" to its command Product: Portable OpenSSH Version: 7.1p1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: ssh Assignee:
2010 Jan 18
1
changing openoffice defaults
...at googlemail.com>wrote: > > > Hi, > I am trying to change some OpenOffice defaults. First of all I would like > to change the default open/save directory. > First I tried to change *$work* in */opt/ > openoffice.org/basis3.1/share/registry/data/org/openoffice/Office/Paths.xcu > * but it hadn't had any impact on the users. > Then I tried to change the file */opt/ > openoffice.org/basis3.1/share/registry/schema/org/openoffice/Office/Common.xcs > * > I tried to change : > *<prop oor:name="Work" oor:type="xs:string"> >...
2018 Jul 06
4
Bash question
Hi All, I am trying to build a command line with spaces in the argument. This demonstrates what I am trying to do. Clearly the first two commands work fine. However, the last 4 lines to not. /opt/libreoffice5.4/program/soffice.bin --headless --convert-to csv "/tmp/file.xlsx" /opt/libreoffice5.4/program/soffice.bin --headless --convert-to csv "/tmp/file 2.xlsx" MSG="file
2004 Jul 22
3
[fdo] Scheduling subsystems (crontab, at) and the desktop
Hi there fellow hackers, geeks and others who want the UNIX desktop to succeed. I bring forward the question whether or not a (freedesktop.org) specification is necessary for application scheduling software. The current UNIX Desktop user does not have an easy way to configure the tasks which he wants to schedule. Sure we have such a utility. And sure we can shout to our Desktop users