search for: ffunction

...config.status config.status: creating openh323u.mak config.status: creating Makefile config.status: creating include/openh323buildopts.h [root@kamran openh323]# make opt set -e; make -C src opt; make -C samples/simple opt; make[1]: Entering directory `/openh323/src' g++ -DP_LINUX=2.6.5-1.358 -ffunction-sections -fdata-sections -D_REENTRANT -Wall -fPIC -DP_USE_PRAGMA -DPHAS_TEMPLATES -I/pwlib/include/ptlib/unix -I/usr/include/pwlib -DPTRACING -I/openh323/include -DHAS_OSS -DPTRACING -I/pwlib/include -fPIC -DP_USE_PRAGMA -Os -DNDEBUG -x c++ -c h225_1.cxx -o /openh323/lib/obj_linux_x86_r/h225_1.o...

...<kledzik at apple.com> wrote: >> On Jul 30, 2013, at 4:28 PM, Eric Christopher wrote: >>> On Mon, Jul 29, 2013 at 9:24 AM, Nick Kledzik <kledzik at apple.com> wrote: >>>> On Jul 25, 2013, at 2:10 PM, Rui Ueyama wrote: >>>>> Is there any reason -ffunction-sections and -fdata-sections wouldn't work? If it'll work, it may be be better to say "if you want to get a better linker output use these options", rather than defining new ELF section. >>>> From my understanding, -ffunction-sections is a good semantic match. But it...

On Jul 30, 2013, at 4:28 PM, Eric Christopher wrote: > On Mon, Jul 29, 2013 at 9:24 AM, Nick Kledzik <kledzik at apple.com> wrote: >> >> On Jul 25, 2013, at 2:10 PM, Rui Ueyama wrote: >>> Is there any reason -ffunction-sections and -fdata-sections wouldn't work? If it'll work, it may be be better to say "if you want to get a better linker output use these options", rather than defining new ELF section. >> >> From my understanding, -ffunction-sections is a good semantic match. But i...

...lt;kledzik at apple.com> wrote: > > On Jul 30, 2013, at 4:28 PM, Eric Christopher wrote: >> On Mon, Jul 29, 2013 at 9:24 AM, Nick Kledzik <kledzik at apple.com> wrote: >>> >>> On Jul 25, 2013, at 2:10 PM, Rui Ueyama wrote: >>>> Is there any reason -ffunction-sections and -fdata-sections wouldn't work? If it'll work, it may be be better to say "if you want to get a better linker output use these options", rather than defining new ELF section. >>> >>> From my understanding, -ffunction-sections is a good semantic match....

...t the goal is faster links and better dead code stripping? Making that clearer would help. Naming your sections something other than "safe" (which has *very* different connotations) would help more. However, I question several fundamental assumptions: 1) We should be very certain that -ffunction-sections is not a viable solution as it exists and is well supported in other toolchains and environments. 2) We should talk to other ELF producers and coordinate to make sure we don't end up creating a twisty maze of extensions here. 3) We should step back and consider leapfrogging to a full...

On Jul 25, 2013, at 2:10 PM, Rui Ueyama wrote: > Is there any reason -ffunction-sections and -fdata-sections wouldn't work? If it'll work, it may be be better to say "if you want to get a better linker output use these options", rather than defining new ELF section. >From my understanding, -ffunction-sections is a good semantic match. But it introduces a...

...eel like a win. So once again, what actual > advantages for ELF or COFF have been created by the atom model? Mach-O > hardly counts as it doesn't allow the flexibility of the section model > as has been discussed before. > The atom model is optimized when you compile the code with -ffunction-sections and -fdata-sections. Once targets start having -fno-unique-section-names as the default the atom model looks more promising. Everyone likes to have the image size small, and making -ffunction-sections/-fdata-sections (or) -fno-unique-section-names the default make sense and the atom m...

...ich has *very* different connotations) would help more. "safe" is a property of a section, by which a section can be atomized and the atoms can appear anywhere in the final output file. > > However, I question several fundamental assumptions: > 1) We should be very certain that -ffunction-sections is not a viable > solution as it exists and is well supported in other toolchains and > environments. -ffunction-sections and -fdata-sections would work, but that would require all third party libraries etc to make sure that they are all compiled with -ffunction-sections. > 2) W...

...system...) NOW I HAVE THIS ERROR: [root@pbx asterisk-oh323-0.7.0]# make for x in wrapper asterisk-driver; do make -C $x build || exit 1 ; done make[1]: Entering directory `/root/asterisk-oh323-0.7.0/wrapper' ./check_ver /root/pwlib pwlib ./check_ver /root/openh323 openh323 g++ -DP_USE_PRAGMA -ffunction-sections -fdata-sections -D_REENTRANT -DOPENSSL_NO_KRB5 -Wall -fPIC -I/root/pwlib/include -DPTRACING -I/root/openh323/include -DHAS_OSS -Wall -x c++ -Os -DWRAPTRACING -DWRAPTRACING_LEVEL=5 -DPWLIBVERSION=\"1.6.6\" -DOPENH323VERSION=\"1.13.5\" -I/root/pwlib/include/ptlib/unix -...

...retation of "safe" is going to shared by anyone who hasn't read this email from you. ;] It would need a better name, but I'm not sure we need it at all, see below. > > >> However, I question several fundamental assumptions: >> 1) We should be very certain that -ffunction-sections is not a viable >> solution as it exists and is well supported in other toolchains and >> environments. >> > -ffunction-sections and -fdata-sections would work, but that would require > all third party libraries etc to make sure that they are all compiled with >...

On Mon, Jul 29, 2013 at 9:24 AM, Nick Kledzik <kledzik at apple.com> wrote: > > On Jul 25, 2013, at 2:10 PM, Rui Ueyama wrote: >> Is there any reason -ffunction-sections and -fdata-sections wouldn't work? If it'll work, it may be be better to say "if you want to get a better linker output use these options", rather than defining new ELF section. > > From my understanding, -ffunction-sections is a good semantic match. But it introdu...

...nerated call graph profile. The current approach can actually do this by embedding it into an extra object file. > > > It doesn't currently work for LTO as the llvm pass needs to be run after >> all inlining decisions have been made and LTO codegen has to be done with >> -ffunction-sections. >> > So this is just an implementation issue, right? You can make LTO run with > -ffunction-sections (by setting TargetOptions.FunctionSections=true) and > insert your pass in the appropriate place in the pipeline. > Yeah, just an implementation issue. Just need to buil...

Is there any reason -ffunction-sections and -fdata-sections wouldn't work? If it'll work, it may be be better to say "if you want to get a better linker output use these options", rather than defining new ELF section. On Thu, Jul 25, 2013 at 2:01 PM, Shankar Easwaran <shankare at codeaurora.org>wrote:...

...39;s no direct reference to the symbol > data. All references should go through relocations. A section may contain > both "safe" and "unsafe" symbols. Sections contain symbols. In the context of ELF, marking sections as safe/not is more desirable because of the switches (-ffunction-sections and -fdata-sections available already). > - How about making the compiler to create a new section for each "safe" > atom, as it does for inline functions? You already have a switch called -ffunction-sections and -fdata-sections to put function and data in seperate sect...

...ple cc'ed, and I may be too cautious, but I'd hesitate to define a new ELF section if there's other mean already available to achieve the same thing. On Thu, Jul 25, 2013 at 2:12 PM, Shankar Easwaran <shankare at codeaurora.org>wrote: > Not all users compile their code with -ffunction-sections and > -fdata-sections. > > This is to handle usecases when libraries use a mix of object files too. > > > > On 7/25/2013 4:10 PM, Rui Ueyama wrote: > >> Is there any reason -ffunction-sections and -fdata-sections wouldn't work? >> If it'll work,...

Not all users compile their code with -ffunction-sections and -fdata-sections. This is to handle usecases when libraries use a mix of object files too. On 7/25/2013 4:10 PM, Rui Ueyama wrote: > Is there any reason -ffunction-sections and -fdata-sections wouldn't work? > If it'll work, it may be be better to say "if you want...

...Wextra -Wno-unused-parameter > -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic > -Wno-long-long -Wimplicit-fallthrough -Wcovered-switch-default > -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor > -Wstring-conversion -fdiagnostics-color -ffunction-sections > -fdata-sections -fno-common -Woverloaded-virtual -Wno-nested-anon-types > -O3 -DNDEBUG  -Wl,-allow-shlib-undefined > -Wl,-rpath-link,/home/laguest/src/mine-new/llvm/llvm-project/build/./lib >  -Wl,-O3 -Wl,--gc-sections > tools/clang/tools/extra/clang-ch...

On Jul 29, 2013, at 10:09 AM, Shankar Easwaran wrote: > On 7/29/2013 11:24 AM, Nick Kledzik wrote: >> On Jul 25, 2013, at 2:10 PM, Rui Ueyama wrote: >>> Is there any reason -ffunction-sections and -fdata-sections wouldn't work? If it'll work, it may be be better to say "if you want to get a better linker output use these options", rather than defining new ELF section. >> >From my understanding, -ffunction-sections is a good semantic match. But it intr...

...this by >> embedding it into an extra object file. >> >> >>> >>> >>> It doesn't currently work for LTO as the llvm pass needs to be run after >>>> all inlining decisions have been made and LTO codegen has to be done with >>>> -ffunction-sections. >>>> >>> So this is just an implementation issue, right? You can make LTO run >>> with -ffunction-sections (by setting TargetOptions.FunctionSections=true) >>> and insert your pass in the appropriate place in the pipeline. >>> >> >&...

...r=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wcovered-switch-default -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wstring-conversion -fdiagnostics-color -ffunction-sections -fdata-sections -fno-common -Woverloaded-virtual -Wno-nested-anon-types -O3 -DNDEBUG -Wl,-allow-shlib-undefined -Wl,-rpath-link,/home/laguest/src/mine-new/llvm/llvm-project/build/./lib -Wl,-O3 -Wl,--gc-sections tools/clang/tools/extra/clang-change-namespace/tool/CMakeFiles/clang-change-n...