similar to: [LLVMdev] Type conflicts with linkonce functions

On Jun 12, 2008, at 11:56 PM, Nathan Keynes wrote: > Hi, > > Currently if the linker encounters a pair of linkonce function > definitions with different types, it raises an error of the form: > > llvm-ld: error: Cannot link file 'item.o.bc': Function > '_ZN18st_select_lex_unit12first_selectEv' defined as both ' > %struct.SELECT_LEX*

On 20/06/2008, at 3:30 PM, Chris Lattner wrote: > > On Jun 12, 2008, at 11:56 PM, Nathan Keynes wrote: > >> Hi, >> >> Currently if the linker encounters a pair of linkonce function >> definitions with different types, it raises an error of the form: >> >> llvm-ld: error: Cannot link file 'item.o.bc': Function >>

Before I go writing a bug report, I want to know if the behavior I am seeing is intended. Before 1.3, I was able to generate a linkonce definition in one module, and an external declaration in another module and link them together, with the result being a defined symbol with external linkage. However, with the latest head, it apparently discards the linkonce version, and my output contains

On Jun 9, 2008, at 7:13 PM, Talin wrote: > Before I go writing a bug report, I want to know if the behavior I am > seeing is intended. > > Before 1.3, I was able to generate a linkonce definition in one > module, > and an external declaration in another module and link them together, > with the result being a defined symbol with external linkage. However, > with the

Hi Nick, Bigcheese, I wanted to add support to support .gnu.linkonce sections in the resolver. _*About .gnu.linkonce sections*_ .gnu.linkonce sections were primarily present in ELF that was used in a way to model COMDAT in early ELF implementations. We have seen usecases of .gnu.linkonce sections used in various object files(mainly libc), and I think its much needed to support this style in

http://llvm.org/docs/LangRef.html#linkage-types says: Globals with “linkonce” linkage are merged with other globals of the same name when linkage occurs. This can be used to implement some forms of inline functions, templates, or other code which must be generated in each translation unit that uses it, but where the body may be overridden with a more definitive definition later. Unreferenced

I'm using LLVM to compile one of the MYSQL libraries and then generate assembly using llc and compile that with gcc to create the lib and link with the rest of the system. I'm able to compile llc output with gcc without any problem. However, when I try to link the server with the library compiled with LLVM I get the following error during linking:

Hi, I've had problem with a program using LLVM that tried to dynamic_cast objects created in the JIT execution engine, from the native part of the program (for the curious, the program is PinaVM http://gitorious.org/pinavm/pages/Home). I've narrowed down the issue to the linkage of weak_odr and linkonce_odr symbols, used for the vtables, and that _must_ be unique for dynamic_cast to

On Tue, Oct 24, 2017 at 9:27 PM, Vedant Kumar <vsk at apple.com> wrote: > Unreferenced linkonce globals are allowed to be discarded. > > > Is __udivmodti4 referenced? > It's referenced by a different .o file, but nothing within the module. My confusion comes from the missing direct object in the sentence. Referenced by a function local to the module? Referenced by any

On Oct 29, 2013, at 9:52 PM, Shankar Easwaran wrote: > I am trying to implement support for handling section groups in lld. > > There are two ways of figuring out section groups with ELF. > > a) Sections with SHF_GROUP property > b) .gnu.linkonce sections (the signature identified by the name of the section) -- This was the method to coalesce similiar constants. > >

On 10/30/2013 12:53 AM, Nick Kledzik wrote: > On Oct 29, 2013, at 9:52 PM, Shankar Easwaran wrote: >> I am trying to implement support for handling section groups in lld. >> >> There are two ways of figuring out section groups with ELF. >> >> a) Sections with SHF_GROUP property >> b) .gnu.linkonce sections (the signature identified by the name of the section)

Hi Nick, I am trying to implement support for handling section groups in lld. There are two ways of figuring out section groups with ELF. a) Sections with SHF_GROUP property b) .gnu.linkonce sections (the signature identified by the name of the section) -- This was the method to coalesce similiar constants. Section Groups(SHF_GROUP) is the preferred way on ELF but .gnu.linkonce sections is

Hi, a few days there was thread about Centos Plus mysql. Today Mysql released mysql-5.0.51a. Where does Centos Plus mysql-5.0.54 come from? Thanks, David

Hey everyone, This is the first time I've ever used a mailing-list so bear with me :-) I've just got a new dedicated server from Hostik and they've installed CentOS 5.2 on the system (awesome!) and came pre-installed with PHP, MySQL, and Apache (among other things). I noticed that PHP version is 5.1.6, the MYSQL is 5.0.45, and Apache is 2.2.3 I ran yum to update, thinking it would

Hi, I am trying to build and install LLVM onto a current Debian Linux system using gcc4 frontend binaries for Red Hat Enterprise Linux4/x86 . Using the commands below the Build finishes, ignoring an error that comes up again when I try to make install. See the messages below. I have no good feeling about the "-i -k" options. Is it OK? Thank you in advance for any advice and best

I'm trying to build the MySQL components in asterisk-addons but no luck so far. I hope that you can help. I have MySQL installed. rpm -qa indicates: MySQL-server-5.0.22-0 MySQL-devel-5.0.22-0 MySQL-client-5.0.22-0 rpm -ql MySQL-devel | grep client indicates: /usr/lib/mysql/libmysqlclient.a /usr/lib/mysql/libmysqlclient.la /usr/lib/mysql/libmysqlclient_r.a /usr/lib/mysql/libmysqlclient_r.la

On Mon, 12 Feb 2007, Carsten Reuter wrote: > I am trying to build and install LLVM onto a current Debian Linux system > using gcc4 frontend binaries for Red Hat Enterprise Linux4/x86 . > Using the commands below the Build finishes, ignoring an error that > comes up again when I try to make install. > See the messages below. I have no good feeling about the "-i -k" options.

We need to build with -mno-pic to disable all uses of GP, as well as use a custom linker script to avoid collisions between klibc.so's and the executable's segments. Signed-off-by: James Clarke <jrtc27 at jrtc27.com> --- usr/klibc/arch/ia64/MCONFIG | 3 + usr/klibc/arch/ia64/crt0.S | 4 - usr/klibc/arch/ia64/klibc.ld | 267 ++++++++++++++++++++++++++++++++++++++++++

Commit-ID: 048bfb0df170d4a43142adcee8a2dffdfc2c1e9f Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=048bfb0df170d4a43142adcee8a2dffdfc2c1e9f Author: James Cowgill <james.cowgill at mips.com> AuthorDate: Fri, 2 Mar 2018 08:33:01 -0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Wed, 2 Jan 2019 03:08:04 +0000 [klibc] mips: use -Ttext-segment

Commit-ID: 8418552770110e9864ab24d60d8481fac58d3a65 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=8418552770110e9864ab24d60d8481fac58d3a65 Author: James Clarke <jrtc27 at jrtc27.com> AuthorDate: Mon, 21 Jan 2019 21:26:57 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Mon, 21 Jan 2019 22:51:27 +0000 [klibc] ia64: Fix shared build We