> AFAIU, having the shared libraries in separate files means they are
> not "combined" with the program's code. That's how I understand what
> RMS told me back then, in the quote that I brought up.
Nothing in the GCC Runtime Exception says that the "Target Code" consists
of a single file.
> Date: Thu, 17 Jul 2025 05:23:50 -0700 (PDT)
> Cc: gcc@gcc.gnu.org, jwakely@gmail.com, qifan.z...@xpeedic.com
> From: ken...@adacore.com (Richard Kenner)
>
> > I don't see how distributing in the same tarball would solve the
> > problem.
> >
> > Suppose I'd decide to distribute a Windows bui
> I don't see how distributing in the same tarball would solve the
> problem.
>
> Suppose I'd decide to distribute a Windows build of Emacs together
> with GNU Grep (e.g., because MS-Windows systems don't come with Grep
> OOTB, whereas Emacs users need Grep for several of its features). I
> would
> Date: Thu, 17 Jul 2025 03:43:29 -0700 (PDT)
> Cc: gcc@gcc.gnu.org, jwakely@gmail.com, qifan.z...@xpeedic.com
> From: ken...@adacore.com (Richard Kenner)
>
> > > Yes, but the discussion wasn't about "as a separate file", but as a file
> > > that's part of the distribution of another program.
> > Yes, but the discussion wasn't about "as a separate file", but as a file
> > that's part of the distribution of another program.
>
> A shared library is always a separate file.
Yes, of course. What I meant is that it's not *being distributed
separately*. For example, it can be in the same t
> Date: Thu, 17 Jul 2025 02:28:36 -0700 (PDT)
> Cc: gcc@gcc.gnu.org, jwakely@gmail.com, qifan.z...@xpeedic.com
> From: ken...@adacore.com (Richard Kenner)
>
> > That's not what RMS told me when I asked him some time ago. He said
> > that, since libgcc DLL and libstdc++ DLL are basically separ
> That's not what RMS told me when I asked him some time ago. He said
> that, since libgcc DLL and libstdc++ DLL are basically separate files
> and thus separate builds of the libraries, the run-time exception you
> pointed to is not applicable to them. Quoting his response back then:
>
> Ther
> Date: Wed, 16 Jul 2025 19:03:21 +0200
> Cc: qifan.z...@xpeedic.com, gcc@gcc.gnu.org
> From: David Brown
>
> >> Well they didn't ask about distributing the DLLs :-)
> >
> > They did, indirectly: programs compiled by MinGW GCC are linked
> > against libgcc and libstdc++ import libraries, and thu
On 16/07/2025 17:37, Eli Zaretskii via Gcc wrote:
From: Jonathan Wakely
Date: Wed, 16 Jul 2025 16:12:01 +0100
Cc: qifan.z...@xpeedic.com, gcc@gcc.gnu.org
On Wed, 16 Jul 2025 at 15:59, Eli Zaretskii wrote:
Please stop giving bad advice and direct people to read the
appropriate documentation.
> Date: Wed, 16 Jul 2025 17:44:41 +0200
> From: Dennis Luehring via Gcc
>
> Am 16.07.2025 um 17:37 schrieb Eli Zaretskii via Gcc:
> > Unless the Windows loader can find them on
> > the end-user's machine, it will refuse to run the program.
>
> the initial question was: do they fall under GPL whe
Am 16.07.2025 um 17:37 schrieb Eli Zaretskii via Gcc:
Unless the Windows loader can find them on
the end-user's machine, it will refuse to run the program.
the initial question was: do they fall under GPL when just using gcc -
how complex or error prone their distribution concepts get is of no
> From: Jonathan Wakely
> Date: Wed, 16 Jul 2025 16:12:01 +0100
> Cc: qifan.z...@xpeedic.com, gcc@gcc.gnu.org
>
> On Wed, 16 Jul 2025 at 15:59, Eli Zaretskii wrote:
> >
> > > Please stop giving bad advice and direct people to read the
> > > appropriate documentation.
> >
> > Why the animosity?
On Wed, 16 Jul 2025 at 15:59, Eli Zaretskii wrote:
>
> > From: Jonathan Wakely
> > Date: Wed, 16 Jul 2025 15:08:50 +0100
> > Cc: qifan.z...@xpeedic.com, gcc@gcc.gnu.org
> >
> > > > AFAIU, this is accurate if libgcc and libstdc++ are linked statically,
> > > > but not if the program is linked to t
> From: Jonathan Wakely
> Date: Wed, 16 Jul 2025 15:08:50 +0100
> Cc: qifan.z...@xpeedic.com, gcc@gcc.gnu.org
>
> > > AFAIU, this is accurate if libgcc and libstdc++ are linked statically,
> > > but not if the program is linked to their DLL versions (and therefore
> > > the DLLs must be distribut
On Wed, 16 Jul 2025 at 15:06, Jonathan Wakely wrote:
>
> On Wed, 16 Jul 2025 at 13:21, Eli Zaretskii wrote:
> >
> > > Date: Wed, 16 Jul 2025 11:12:44 +0100
> > > Cc: gcc , gcc-help
> > > From: Jonathan Wakely via Gcc
> > >
> > > On Wed, 16 Jul 2025 at 10:06, Qifan.Zhou via Gcc wrote:
> > > >
>
On Wed, 16 Jul 2025 at 13:21, Eli Zaretskii wrote:
>
> > Date: Wed, 16 Jul 2025 11:12:44 +0100
> > Cc: gcc , gcc-help
> > From: Jonathan Wakely via Gcc
> >
> > On Wed, 16 Jul 2025 at 10:06, Qifan.Zhou via Gcc wrote:
> > >
> > > Dear GCC Team,
> >
> > Please don't email both gcc@gcc.gnu.org and
> Date: Wed, 16 Jul 2025 06:49:23 -0700 (PDT)
> Cc: gcc@gcc.gnu.org, jwakely@gmail.com, qifan.z...@xpeedic.com
> From: ken...@adacore.com (Richard Kenner)
>
> > Not if we are talking about Windows binaries intended to be used by
> > people who don't have GCC installed. (The OP asked about Min
> Not if we are talking about Windows binaries intended to be used by
> people who don't have GCC installed. (The OP asked about MinGW, which
> is why I bring up this case.) These DLLs are part of the MinGW GCC
> installation, but do not come with the OS OOTB.
But then what the OP could do is to
> Date: Wed, 16 Jul 2025 06:20:42 -0700 (PDT)
> Cc: gcc@gcc.gnu.org, jwakely@gmail.com, qifan.z...@xpeedic.com
> From: ken...@adacore.com (Richard Kenner)
>
> > AFAIU, this is accurate if libgcc and libstdc++ are linked statically,
> > but not if the program is linked to their DLL versions (an
> AFAIU, this is accurate if libgcc and libstdc++ are linked statically,
> but not if the program is linked to their DLL versions (and therefore
> the DLLs must be distributed with the resulting program). In the
> latter case, the LGPL exception doesn't apply, and distributing these
> DLLs falls u
> Date: Wed, 16 Jul 2025 11:12:44 +0100
> Cc: gcc , gcc-help
> From: Jonathan Wakely via Gcc
>
> On Wed, 16 Jul 2025 at 10:06, Qifan.Zhou via Gcc wrote:
> >
> > Dear GCC Team,
>
> Please don't email both gcc@gcc.gnu.org and gcc-h...@gcc.gnu.org, pick
> the appropriate one. You're not discussin
On Wed, 16 Jul 2025 at 10:06, Qifan.Zhou via Gcc wrote:
>
> Dear GCC Team,
Please don't email both gcc@gcc.gnu.org and gcc-h...@gcc.gnu.org, pick
the appropriate one. You're not discussing development of GCC so this
belongs on the gcc-help list.
Anyway ...
> I hope this message finds you well.
On Tue, Dec 15, 2020 at 05:02:24PM +0100, Thomas Schwinge wrote:
> Per the 'fold_convert_loc' code (cited below), we see that for 'type' of
> 'case INTEGER_TYPE' etc. -- which 'type' of 'case REFERENCE_TYPE' does
> "fall through" into -- we do not handle 'arg' of 'REAL_CST' like we do
> for 'type'
On 5/30/19 8:28 AM, Martin Sebor wrote:
> On 5/30/19 3:12 AM, Fredrik Hederstierna wrote:
>> Hi
>>
>> When reading the SEI CERT C Coding Standard rules, looking at
>> "DCL30-C. Declare objects with appropriate storage durations"
>> it seem like GCC does not warn in compile-time for some noncomplian
On 5/30/19 3:12 AM, Fredrik Hederstierna wrote:
Hi
When reading the SEI CERT C Coding Standard rules, looking at
"DCL30-C. Declare objects with appropriate storage durations"
it seem like GCC does not warn in compile-time for some noncompliant examples.
I know eg AddressSanitizer and several ru
On 24/08/18 14:51, Akhilesh chirlancha wrote:
> Hello All,
>
> I'm using gcc 5.4.0 for armhf target.
>
> I was compiling simple stack over flow test code with '-mapcs-stack-check'
> option.
> # gcc -mapcs-stack-check test.c
> test.c:1:0: warning: -mapcs-stack-check incompatible with -mno-apcs-fra
On 24/07/18 09:40, Fredrik Hederstierna wrote:
> Hi
>
> This is a general question to all you working with GCC benchmarking.
>
> I have been working with code benchmarks like CSiBE for ARM. From
> time to time unpredicted results appears where numbers gets worse by
> no reason.
>
> When looking
On Tue, 24 Jul 2018, Fredrik Hederstierna wrote:
> So my question is how to approach this problems when doing benchmarking,
> ofcourse we want the benchmark to mirror as near as 'real life' code as
> possible. But if code contains real bugs, and issues that could cause
> unpredictable code genera
On 07/29/2017 07:37 AM, Segher Boessenkool wrote:
On Mon, Jul 24, 2017 at 01:08:35PM -0600, Martin Sebor wrote:
...or more precisely, about MoinMoin hyperlink formatting.
I'd like to insert hyperlinks to anchors in the GCC HTML manual
on some Wiki pages. Specifically, I'd like to be able to li
On Mon, Jul 24, 2017 at 01:08:35PM -0600, Martin Sebor wrote:
> ...or more precisely, about MoinMoin hyperlink formatting.
>
> I'd like to insert hyperlinks to anchors in the GCC HTML manual
> on some Wiki pages. Specifically, I'd like to be able to link
> to the description of a command line opt
Dear Samuel,
(I copy this email to the gcc@gcc.gnu.org list, as this is the home for
discussions of this library.)
You can't use the libquadmath library with an ANSI-C compiler. You need a
compiler that supports the __float128 type and operations on it (such as
multiplications, as you mention)
On 2 June 2010 22:42, manal habib wrote:
> Hi,
>
> I am new into the field of coding, and I am wandering if I can get
> some help on how to use the GCC? I have a mac version 10.5.8. Should
> I just copy one of the image folders to make computer? how can use
> it?
This is not the right mailing l
On 12 April 2006 22:18, Mark Cuss wrote:
The
guy who was here before me set up the previous version (gcc-3.3.3)
gcc 3.3.3 was compiled with the following configure flags:
configure --with-gnu-as --with-as=/cdl/apps/bin/sun/as --with-gnu-ld
--with-ld=/cdl/apps/bin/sun/ld --enable-lang
On 12 April 2006 22:18, Mark Cuss wrote:
> The
> guy who was here before me set up the previous version (gcc-3.3.3)
> gcc 3.3.3 was compiled with the following configure flags:
> configure --with-gnu-as --with-as=/cdl/apps/bin/sun/as --with-gnu-ld
> --with-ld=/cdl/apps/bin/sun/ld --enable-lan
On 4/13/06, Mark Cuss <[EMAIL PROTECTED]> wrote:
> Hello - this is definitely a newbie question, so bear with me...
>
> We've been using gcc under Solaris on SPARC hardware for some time now. The
> guy who was here before me set up the previous version (gcc-3.3.3) and now
> I'm trying to get gcc-3
From: "Jim Wilson" <[EMAIL PROTECTED]>
> Paul Albrecht wrote:
> > Is there some reason gcc hasn't been or can't be enhanced to provide output
> > for
> > cross-referencing programs?
>
> FYI, there are a number of tools available for producing
> cross-referencing info. See for instance
> htt
Paul Albrecht wrote:
Is there some reason gcc hasn't been or can't be enhanced to provide output for
a cross-referencing
programs?
FYI, there are a number of tools available for producing
cross-referencing info. See for instance
http://www.gnu.org/software/global/links.html
and try look
From: "Robert Dewar" <[EMAIL PROTECTED]>
> Paul Albrecht wrote:
> > Is there some reason gcc hasn't been or can't be enhanced to provide output
> > for a
> > cross-referencing programs?
> >
>
> No reason why it can't be, and the reason it hasn't is that no one has done
> it. Actually strictly
yo
Paul Albrecht wrote:
Is there some reason gcc hasn't been or can't be enhanced to provide output for
a cross-referencing
programs?
Paul Albrecht
No reason why it can't be, and the reason it hasn't is that
no one has done it. Actually strictly you don't mean gcc
here, you are referring to part
Thanks for clearing up my mis-understanding !
--- Andrew Pinski <[EMAIL PROTECTED]> wrote:
>
> On Feb 22, 2005, at 4:29 PM, Vasanth wrote:
>
> > Hi,
> >
> > I am sure this bug has been reported before, but I
> am
> > not able to track it down in bugzilla. Someone
> kindly
> > refer me to the r
On Feb 22, 2005, at 4:29 PM, Vasanth wrote:
Hi,
I am sure this bug has been reported before, but I am
not able to track it down in bugzilla. Someone kindly
refer me to the relevant bug report.
You are violating C90/C99 aliasing rules.
--Pinski
41 matches
Mail list logo
