Displaying 7 results from an estimated 7 matches for "data_seg".
Did you mean:
data_set
2001 Apr 10
3
DLL at fixed location and memory sharing between executables
Is there a way to get the following to work under WINE? (i.e. to get two
executables to share global memory as they do under windows)
We have a DLL that is at a specified memory location.
At the top of the code a variable is declared as follows:
#pragma data_seg( "global_mem" )
#pragma bss_seg( "global_mem" )
unsigned uAttachmentCount = 0;
Now..
The main program links to that DLL and as part of the DllMain it increments
that count.
The main program executes another program. That other program also links
to that DLL.
Under Windows t...
2001 Sep 05
4
Problems trying to run the examples in windows v orbis sdk
Yes, it works now.
Thank you very much.
-----Original Message-----
From: Chris Wolf [mailto:cwolf@starclass.com]
Sent: 05 September 2001 10:12
To: vorbis-dev@xiph.org
Subject: Re: [vorbis-dev] Problems trying to run the examples in windows
vorbis sdk
On 9/4/2001 at 6:00 PM Pablos-Sanchez, Rolando wrote:
>I have just downloaded the vorbis sdk for windows, for researching
>purposes.
>
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,rather
2011 Mar 06
1
PXELINUX Debugging Output
I am sending a patch that makes the debugging output of PXELINUX slightly
more concise, without (intentionally) affecting its completeness at all.
Additionally, I am proposing that the debugging output of PXELINUX --
specifically the messages that appear after the copyright statement, but
before the menu is loaded -- only be shown in response to keyboard input
(such as holding Shift or Alt, or
2012 Sep 10
3
[LLVMdev] Question about ctors, dtors and sections on Windows
Hello 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
2017 Mar 14
2
[cfe-dev] proposal - pragma section directive in clang
...ouldn't be right -
don't we need to use attributes when dropping metadata would cause
miscompiles?
I was considering adding an attributeset to global variables, so we'd have
something like:
global i32* @g = i32 0, #0
#0 = attributes {bss_seg="...", text_seg="...", data_seg="..."}
Cheers,
James
On Tue, 14 Mar 2017 at 18:15 Reid Kleckner <rnk at google.com> wrote:
> Is that actually an important use case? It sounded like it wasn't, and if
> we pursue option 3, we need to staple three pieces of data to every global:
> the default sectio...
2017 Mar 14
2
[cfe-dev] proposal - pragma section directive in clang
Thanks Reid/Jonathon for your replies.
Reid,
An important case against module level flags is that it wont allow changing or resetting section names e.g.
int a;
#pragma clang section bss = "xyz"
int b;
In case above, users would like to see only 'b' placed in 'xyz' and not 'a' as well.
Link pointed to by Jonathon seems to require same behavior.