search for: sf_hidden

...258665 I added a line to set the SF_Exported flag in COFFObjectFile - the JIT needs this flag to distinguish exported symbols from non-exported ones. In the process of trying to write a test case for that, a couple of questions came up: (1) Previously COFF wasn't setting either SF_Exported or SF_Hidden. What is the linker using to build the export table for DSOs? Is it just checking the COFF flags directly? (2) Is there any situation where 'SF_Exported' isn't just the inverse of 'SF_Hidden'? Can we get rid of one or the other of those flags? (3) It looks like the symbol tabl...

...tains additional flags that the linker takes under consideration. __declspec(dllexport) is typically implemented by adding a /EXPORT entry for a particular symbol in there (e.g. /EXPORT:_foo). Ok. > > (2) Is there any situation where 'SF_Exported' isn't just the inverse of 'SF_Hidden'? Can we get rid of one or the other of those flags? > I don't believe so. Normal static functions will have local binding but default visibility. Such a function would be neither hidden nor exported. Something feels not-quite-right about this. What are the valid values for visibility...