Re: [cfe-users] Linking error and memory bloating for .so file creation

[Ankush Sharma via cfe-users]

 Hi,

We are generating the .so file for the Android ARM 64 flavor on Windows
platform.
Following is the version info for the "clang++.exe" executable used for
generating the .so file.


*F:\Debug>"F:\androidndk.16.1.9\toolchains\llvm\prebuilt\windows-x86_64\bin\clang++.exe"
-v*
- Android clang version 5.0.300080  (based on LLVM 5.0.300080)
- Target: x86_64-unknown-linux
- Thread model: posix

Note: No I/O error is getting reported during the link run. Also we are
witnessing this issue when moving
from "gnustl" to "LibC++" support for standard C++ library.

The linker flags used are attached with the mail. It would be good if some
linker flags be turned on
to further debug the link run.

On Tue, Mar 12, 2019 at 2:03 PM Csaba Raduly  wrote:

> Hi Ankush,
> On Mon, Mar 11, 2019 at 8:23 PM Ankush Sharma wrote:
> > During the linking stage for an “.so” file creation, an error message is
> being flagged by clang.
> >
> > ld: error: dummy.so: write: Function not implemented
>
> What was the command line that was used to invoke the linker?
> What filesystem are you using?
>
> Csaba
> --
> You can get very substantial performance improvements
> by not doing the right thing. - Scott Meyers, An Effective C++11/14 Sampler
> So if you're looking for a completely portable, 100% standards-conformat
> way
> to get the wrong information: this is what you want. - Scott Meyers
> (C++TDaWYK)
>


-- 
Thanks and Regards
Ankush
-Wl,--no-whole-archive
--gcc-toolchain=f:/androidndk.16.1.9/toolchains/arm-linux-androideabi-4.9/prebuilt/windows-x86_64
--target=armv7-none-linux-androideabi
-Wl,-z,relro
-Wl,-z,now
--sysroot=f:/androidndk.16.1.9/platforms/android-21/arch-arm
-Lf:/androidndk.16.1.9/platforms/android-21/arch-arm/usr/lib
-llog
-lEGL
-lGLESv1_CM
-lOpenSLES
-lGLESv2
-Wl,--dynamic-linker,/system/bin/linker
-Wl,--build-id=sha1
-shared
-Wl,--fix-cortex-a8
-Wl,--gc-sections
-Wl,-z,noexecstack
-Wl,-Bsymbolic
-Wl,--no-undefined
-Wl,--stats
-Wl,--no-map-whole-files
-Wl,--no-wchar-size-warning
-lgcc
-landroid
-lz
-Wl,-rpath-link=f:/androidndk.16.1.9/platforms/android-21/arch-arm/usr/lib
-lstdc++
-lc
-lm___
cfe-users mailing list
cfe-users@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-users

[cfe-users] Where does clang merge two structTypes into one?

[Fuqian Huang via cfe-users]

I want to modified clang and add a attribute some struct fields, but
clang merge two structTypes with same element types into one.
e.g.
%struct.a = type { i16, i16, i8*}
%struct.b = type { i16, i16, i8*}
these two struct types will be merged into one.
What i want is
%struct.a = type { i16, i16, i8*}
%struct.b = type { i16, i16, i8* __my_attribute__ }
I may add one attribute to some field of the struct b, and do not want
these two structs to be merged.
So, where does clang merge same structTypes.
___
cfe-users mailing list
cfe-users@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-users