Hi,
Can I share Counts & Cost for review?
Regards,
Sasha
From: Sasha Grace
Sent: 23 March 2023 12:59 PM
To: 'gcc@gcc.gnu.org'
Subject: RE: FYI - International Microwave Symposium 2023
Hi,
Any update on my previous email?
If YES, please reply back as "Send Counts and
Hi,
Any update on my previous email?
If YES, please reply back as "Send Counts and Pricing".
Regards
Sasha
From: Sasha Grace
Sent: 20 March 2023 07:39 PM
To: gcc@gcc.gnu.org
Subject: FYI - International Microwave Symposium 2023
Hello
Are you interested in purchasing Int
Hello
Are you interested in purchasing International Microwave Symposium 2023 Updated
Database
Attendees:
Design Engineering, Executive/Senior Management, Student, Professor /
Research-Academic, Marketing/Sales, Research & Development-Industry,
Engineering Management, Application Engineer, Exe
On Thu, Sep 16, 2021 at 11:45 AM Martin Sebor via Gcc wrote:
>
> On 9/14/21 2:10 AM, Andrew Pinski via Gcc wrote:
> > Hi all,
> >I am doing some bugzilla cleanup. This includes disabling some
> > components and some versions for new bugs.
> > So far I have disabled versions before GCC 4 becau
On September 17, 2021 6:30:21 PM GMT+02:00, Martin Sebor
wrote:
>On 9/17/21 8:54 AM, Richard Earnshaw wrote:
>>
>>
>> On 16/09/2021 16:44, Martin Sebor via Gcc wrote:
>>> On 9/14/21 2:10 AM, Andrew Pinski via Gcc wrote:
Hi all,
I am doing some bugzilla cleanup. This includes disab
On 9/17/21 8:54 AM, Richard Earnshaw wrote:
On 16/09/2021 16:44, Martin Sebor via Gcc wrote:
On 9/14/21 2:10 AM, Andrew Pinski via Gcc wrote:
Hi all,
I am doing some bugzilla cleanup. This includes disabling some
components and some versions for new bugs.
So far I have disabled versions b
On 16/09/2021 16:44, Martin Sebor via Gcc wrote:
On 9/14/21 2:10 AM, Andrew Pinski via Gcc wrote:
Hi all,
I am doing some bugzilla cleanup. This includes disabling some
components and some versions for new bugs.
So far I have disabled versions before GCC 4 because we have not had a
report
On Thu, Sep 16, 2021 at 11:45 AM Martin Sebor via Gcc wrote:
> ice-on-invalid-code: ICE on code that is not syntactically valid.
> ice-on-valid-code: ICE on code that is syntactically valid.
Presumably, the distinction is there because more attention would get
paid to the latter over the former.
On 9/14/21 2:10 AM, Andrew Pinski via Gcc wrote:
Hi all,
I am doing some bugzilla cleanup. This includes disabling some
components and some versions for new bugs.
So far I have disabled versions before GCC 4 because we have not had a
report from someone for those versions in over 7 years. I
Hi,
On Tue, Sep 14 2021, Andrew Pinski via Gcc wrote:
> Hi all,
> I am doing some bugzilla cleanup. This includes disabling some
> components and some versions for new bugs.
Thanks a lot!
> So far I have disabled versions before GCC 4 because we have not had a
> report from someone for those
Hi all,
I am doing some bugzilla cleanup. This includes disabling some
components and some versions for new bugs.
So far I have disabled versions before GCC 4 because we have not had a
report from someone for those versions in over 7 years. I disabled
some versions which are about developmental
On Tue, 3 Aug 2021 at 18:26, Modi Mo via Gcc wrote:
>
> Hi all,
>
> I recently committed support for the "-fnew-infallible" flag in Clang
> (https://reviews.llvm.org/D105225) to improve non-exceptional performance for
> code that contains exceptions. Having "new" terminate immediately on failure
Hi all,
I recently committed support for the "-fnew-infallible" flag in Clang
(https://reviews.llvm.org/D105225) to improve non-exceptional performance for
code that contains exceptions. Having "new" terminate immediately on failure
stops upward exception propagation and leads to significantly
I don't have any special expertise in this matter, but the
possibility occurs to me that if the caller is an improperly vetted
runtime linked-in agent such as a device driver, then the stack
scrubbing might accidently or intentionally be omitted, reopening
the security hole that stack scrubbing is
I've been working on an implementation of stack scrubbing, strub for
short. It's quite different from the one that Embecosm folks presented
at the Cauldron, in that this one aims to be machine-independent.
Instead of machine-specific tweaking of epilogue logic to zero out a
function's own stack fr
On Tue, 7 Jul 2020, Nino Pereira via Gcc wrote:
> The top line in
> https://gcc.gnu.org/onlinedocs/gcc-4.6.3/gfortran/BOZ-literal-constants.html
>
> says " The syntax is: `prefix quote digits quote', were the prefix is
> either b, o or z,"
>
> Here, 'were' must be 'where'
Thank you for the repor
On Tue, 7 Jul 2020 at 15:41, Nino Pereira via Gcc wrote:
>
> The top line in
> https://gcc.gnu.org/onlinedocs/gcc-4.6.3/gfortran/BOZ-literal-constants.html
>
> says " The syntax is: `prefix quote digits quote', were the prefix is
> either b, o or z,"
>
> Here, 'were' must be 'where'
Thanks. That
The top line in
https://gcc.gnu.org/onlinedocs/gcc-4.6.3/gfortran/BOZ-literal-constants.html
says " The syntax is: `prefix quote digits quote', were the prefix is
either b, o or z,"
Here, 'were' must be 'where'
HTH,
Nino
Hello,
Good Day to you!
Just wanted to check if you would be interested in acquire Fort Lauderdale
International Boat Show 2019 (International Trade Show for Yachting,
Sailing, Boating, Boat Industry, Boat Equipment and Shipping 2019). Attendee
companies to increase prospect flow at your booth -
On Mon, 2018-03-05 at 19:04 +0100, Marek Polacek wrote:
> On Mon, Mar 05, 2018 at 12:58:23PM -0500, Donald Parsons wrote:
> >
> > I am getting ICE bootstrapping gcc-8-20180304.tar.xz when using
> > either
> > isl-0.18 or isl-0.19. I had never had a problem using latest isl
> > over
> > the past
On Mon, 2018-03-05 at 19:04 +0100, Marek Polacek wrote:
> On Mon, Mar 05, 2018 at 12:58:23PM -0500, Donald Parsons wrote:
> >
> > I am getting ICE bootstrapping gcc-8-20180304.tar.xz when using
> > either
> > isl-0.18 or isl-0.19. I had never had a problem using latest isl
> > over
> > the past
On Mon, Mar 05, 2018 at 12:58:23PM -0500, Donald Parsons wrote:
>
> I am getting ICE bootstrapping gcc-8-20180304.tar.xz when using either
> isl-0.18 or isl-0.19. I had never had a problem using latest isl over
> the past couple of years, so a change in gcc last week introduced the
> problem.
>
I am getting ICE bootstrapping gcc-8-20180304.tar.xz when using either
isl-0.18 or isl-0.19. I had never had a problem using latest isl over
the past couple of years, so a change in gcc last week introduced the
problem.
Normally I disable-bootstrap and use last weeks gcc-8 to build this
weeks g
[ This is FYI only. Documenting what I found with gcc 4.5.1 (but is
fixed in 4.5.4 ]
Part of my test suit is to build the kernel with a compiler before asm
goto was supported (to test jump labels without it).
Recently I noticed that the kernel started to hang when building with
it. For a
. Although they may have type char,
>>> short, int, or long (which can have negative values), these bit-fields
>>> have the same range as a bit-field of the same size with the
>>> corresponding unsigned type."
>>>
>>
>> Can you show me where this paragr
On Thu, Jan 22, 2015 at 1:13 PM, Joseph Myers wrote:
> On Thu, 22 Jan 2015, H.J. Lu wrote:
>
>> Here is the link:
>>
>> https://groups.google.com/forum/#!topic/ia32-abi/nq6cvH_VVV4
>
> I sent the following reply to the ia32-abi list but haven't yet received
> it back from the list - you might want
On Thu, 22 Jan 2015, H.J. Lu wrote:
> Here is the link:
>
> https://groups.google.com/forum/#!topic/ia32-abi/nq6cvH_VVV4
I sent the following reply to the ia32-abi list but haven't yet received
it back from the list - you might want to check if it's stuck in
moderation somewhere:
I would sugg
se bit-fields
>> have the same range as a bit-field of the same size with the
>> corresponding unsigned type."
>>
>
> Can you show me where this paragraph in IA-32 psABI?
> I couldn't find it in my copy.
>
FYI :-):
commit 2496a6db377b489668e49c39b6f477a4f8f0ec22
Author: H.J. Lu
Date: Wed Jan 7 13:05:49 2015 -0800
Remove Bit-Fields
--
H.J.
On Thu, Jan 22, 2015 at 11:54 AM, Richard Smith wrote:
> On Thu, Jan 22, 2015 at 4:35 AM, H.J. Lu wrote:
>> Here is the link:
>>
>> https://groups.google.com/forum/#!topic/ia32-abi/nq6cvH_VVV4
>
> The document contains this claim (as do many other psABI documents):
>
> "Bit-fields that are neithe
On Thu, Jan 22, 2015 at 4:35 AM, H.J. Lu wrote:
> Here is the link:
>
> https://groups.google.com/forum/#!topic/ia32-abi/nq6cvH_VVV4
The document contains this claim (as do many other psABI documents):
"Bit-fields that are neither signed nor unsigned
always have non-negative values. Although the
Here is the link:
https://groups.google.com/forum/#!topic/ia32-abi/nq6cvH_VVV4
--
H.J.
Contact Bank Zachodni WBK Poland for your UN Compensation draft worth
$550,000.00
good evening Nick:
i checked and the veneer code generation problem described in
SourceWare BugZilla bug 6727 has not yet been fixed in binutils-2.18,
and that's the latest stable release.
lets see if i can get the latest sources from CVS and then if i
can build and use it.
i will get back to y
Hi,
just an heads-up: today 27_io/basic_stringbuf/setbuf/char/4.cc (and the
wchar_t counterpart) started failing at compile-time at least on x86 and
x86_64: at -O2 the compiler eats all the available memory.
You can see the issue reported here, for example:
http://gcc.gnu.org/ml/gcc-testre
On 5/14/07, Daniel Franke <[EMAIL PROTECTED]> wrote:
SVN update to revision 124718, configured as:
../../svn/gcc/configure
--prefix=/home/daniel/nfs/packages/i686-pc-linux-gnu/gcc
--with-gmp=/home/daniel/nfs/packages/i686-pc-linux-gnu/gmp-4.2.1/
--with-mpfr=/home/daniel/nfs/packages/i686-pc-
SVN update to revision 124718, configured as:
../../svn/gcc/configure
--prefix=/home/daniel/nfs/packages/i686-pc-linux-gnu/gcc
--with-gmp=/home/daniel/nfs/packages/i686-pc-linux-gnu/gmp-4.2.1/
--with-mpfr=/home/daniel/nfs/packages/i686-pc-linux-gnu/mpfr-2.2.1
--disable-nls --enable-threads=po
* Mark Mitchell <[EMAIL PROTECTED]> [2006-03-29 14:54]:
> > GCC 4.1 itself appears to be very stable, both on MIPS and AMD64.
>
> Thank you for doing this, and for reporting the results, and for filing
> the bugs!
I've done the same with a snapshot of GCC 4.2 now on AMD64 (x86_64),
and I'm curren
Matthias Klose wrote:
> Summary:
>
> GCC 4.1 itself appears to be very stable, both on MIPS and AMD64.
Thank you for doing this, and for reporting the results, and for filing
the bugs!
This is, in my opinion, pretty good news for GCC.
Thanks,
--
Mark Mitchell
CodeSourcery
[EMAIL PROTECTED]
(6
Summary:
GCC 4.1 itself appears to be very stable, both on MIPS and AMD64.
There are, however, a large number of packages using code (especially
C++) which GCC 4.1 treats as errors. Fortunately, most of them are
trivial to fix. By compiling about 6200 packages, over 500 new
bugs have been discov
Ralf:
> GCC has its own in-house cranked-up version of 1.4.x libtool.
IOW, I need to tell them to synchronize with libtool, and then
they will eventually commit a new libtool.m4 to their project
and then I can check out if my modifications work or not?
Leif Ekblad
Leif,
* Leif Ekblad wrote on Fri, Jan 13, 2006 at 04:15:30PM CET:
> Peter:
> > Well, it is a daily checkout, please try again to ensure that you did not
> > miss the update on the 13th.. The Changelog for the version that is up
> OK, I saw it was just regenerated. (http://libtool.opendarwin.org/)
Peter:
> Well, it is a daily checkout, please try again to ensure that you did not
> miss the update on the 13th.. The Changelog for the version that is up
there
> now has:
> 2006-01-13 Ralf Wildenhues <[EMAIL PROTECTED]>
>
> ~* libltdl/m4/libtool.m4 (_LT_COMPILER_PIC): Fix my forward por
At approximately 2pm EST, we will be upgrading mysql on sourceware from
version 3.x to version 4.x.
This will cause a short amount of downtime in gcc.gnu.org and
sources.redhat.com Bugzilla and GCC's wiki (< 30 minutes).
--Dan
I've merged the gcc_update --silent changes, and Andreas' quoting fix,
from mainline to the 3.4 and 4.0 branches.
zw
I've added my ACATS/bugzilla table into the the GCC wiki, if we find
something missing let me know.
http://gcc.gnu.org/wiki/ACATS
Laurent
45 matches
Mail list logo
