ib/gcc/x86_64-w64-mingw32/13.3.1/../../../../x86_64-
w64-mingw32/bin/ld.exe: C:\tmp\ccCnskmU.o (symbol from plugin): symbol
`__fpclassify' definition: UNDEF, visibility: DEFAULT, resolution:
RESOLVED_EXEC
attempt to open C:\tmp\ccbENa6D.ltrans0.ltrans.o succeeded
C:\tmp\ccbENa6D.ltrans0.ltrans.o
This is with GNU ld.
--
Eric Botcazou
just aligns
the compiler with the assembler.
Bootstrapped/regtested on SPARC64/Solaris 11, applied on the mainline.
2025-01-18 Eric Botcazou
PR target/118512
* config/sparc/sparc-c.cc (sparc_target_macros): Deal with VIS 3B.
* config/sparc/sparc.cc (dump_target_flag_bits
On Mon, Dec 16, 2024 at 11:43 AM Alexander Monakov wrote:
>
>
> On Mon, 16 Dec 2024, Florian Weimer via Gcc wrote:
>
> > I would like to provide a facility to create wrapper functions without
> > lots of argument shuffling. To achieve that, the wrapping function and
> > the wrapped function shoul
On Sun, Oct 20, 2024 at 9:27 PM Mark Wielaard wrote:
>
> As an experiment Sourceware is now running an forgejo v9 instance at
> https://forge.sourceware.org
>
> Everybody with an @sourceware.org, @cygwin.com or @gcc.gnu.org address
> can register an account (please use the same user name as your a
On Wed, Oct 16, 2024 at 4:29 PM Joseph Myers wrote:
>
> On Wed, 16 Oct 2024, Eric Gallager via Gcc wrote:
>
> > One thing about -Wtraditional is that it enables a lot of different
> > messages, so I always thought it would make more sense as an umbrella
> > warning t
On Wed, Oct 16, 2024 at 2:52 PM Arsen Arsenović via Gcc wrote:
>
> Eli Zaretskii via Gcc writes:
>
> > Please don't remove the support for -Wtraditional if it's easy to fix.
> > Removing it runs risk of breaking someone's program, so unless keeping
> > it is a real dumper on GCC development, I ho
On Mon, Sep 23, 2024 at 8:09 AM Thomas Koenig via Gcc wrote:
>
> [For the fortran people: Discussion on gcc@]
>
> Just a general remark.
>
> There are people, such as myself, who regularly mess up
> their git repositories because they have no mental model
> of what git is doing (case in point: The
On Sat, Sep 14, 2024 at 11:53 AM Jason Merrill via Gcc wrote:
>
> We moved to a bootstrap requirement of C++11 in GCC 11, 8 years after
> support was stable in GCC 4.8.
>
> It is now 8 years since C++14 was the default mode in GCC 6 (and 9 years
> since support was complete in GCC 5); perhaps it's
On Sat, Sep 7, 2024 at 5:34 AM Richard Biener via Gcc wrote:
>
>
>
> > Am 07.09.2024 um 07:27 schrieb Jeremy Rifkin :
> >
> >
> >>
> >> This is why I said what is the a same file if you can't rely on inodes
> >> working?
> >
> > I don't have a good answer for such a case. Of course, no matter h
On Thu, Aug 22, 2024 at 1:27 PM Gerald Pfeifer wrote:
>
> On Mon, 19 Aug 2024, Eric Gallager via Gcc-cvs-wwwdocs wrote:
> > This is an automated email from the git hooks/post-receive script. It was
> > generated because a ref change was pushed to the repository containing
&g
Simple GCC projects page:1. A few references are
> > made to the java front-end.
>
> Indeed, and this is something we (specifically Eric) addressed, together
> with various other issues on this page.
>
> > Under code cleanliness, the bullet for enormous files lists f
I checked this with the
> following spec file:
But you wouldn't have a problem if it was, would you? What happens if the '+'
is changed to another character in the line passed to the driver.
--
Eric Botcazou
racter is not matched by '*' or some such.
--
Eric Botcazou
>
Hi, thanks for creating these. Since "SARIF" is a keyword, what
component should bugs using it generally go under?
Thanks,
Eric
> Dave
>
exploring alternative approaches.
Overall, I hope you find the experience as enriching as I did should you
work on this project! Please feel free to reach out with any questions and
I’ll be more than happy to help where I can.
Best,
Eric
On Tue, Apr 2, 2024 at 10:35 AM Martin Jambor wrote:
> Hell
On Tue, Mar 19, 2024 at 2:10 PM Tom Tromey wrote:
>
> > not sure if the current autoregen.py is in sync with that?
>
> I'm curious why "autoreconf -f" is insufficient.
> It seems to me that this should work.
`autoreconf -f` works fine in individual subdirectories, the problem
is that the top-leve
On Fri, Mar 15, 2024 at 4:53 AM Christophe Lyon via Gcc wrote:
>
> On Thu, 14 Mar 2024 at 19:10, Simon Marchi wrote:
> >
> >
> >
> > On 2024-03-13 04:02, Christophe Lyon via Gdb wrote:
> > > Hi!
> > >
> > > After recent discussions on IRC and on the lists about maintainer-mode
> > > and various p
On Tue, Mar 5, 2024 at 11:01 PM Bradley M. Kuhn via Gcc wrote:
>
> Jeremy, David, Carlos, and the GCC Community,
>
> Jeremy Bennett wrote yesterday:
> > We are starting to put together the plans for this year's Cauldron. We
> > have a suggested date of 13-15 September, the weekend before LPC.
>
>
Hello, I unintentionally stumbled upon some strange behaviour that
occurred due to a typo.
I reproduced the behaviour where an object (std::string in my case) can
be passed to a function by reference, uninitialized, WITHOUT a compiler
warning.
Changing the code to pass the object by value DOES
Personally, since GCC is in stage 3 now, I would push that schedule
back a release and move deprecation to GCC 15, and then only remove it
for GCC 16 if no one objects, but then again I don't actually use
-fgnu-tm myself, so I wouldn't be too upset if the faster schedule is
chosen instead.
Eric Gallager
On Thu, Oct 19, 2023 at 6:43 AM Thomas Schwinge wrote:
>
> Hi!
>
> On 2023-10-19T11:57:33+0200, Andreas Schwab wrote:
> > On Okt 19 2023, Thomas Schwinge wrote:
> >> On 2023-10-18T15:42:18+0100, R jd <3246251196r...@gmail.com> wrote:
> >>> I guess I can ask, why there is not a recursive approach
> You will get the warnings with -pedantic.
> >
> > Martin
> >
> > Am Donnerstag, dem 19.10.2023 um 07:39 -0400 schrieb Eric Sokolowsky via
> > Gcc:
> > > I am using gcc 13.2 on Fedora 38. Consider the following program.
> > >
> > > #
Thank you for your message. Indeed, the -pedantic flag gives me the
warning I expect. -O (as suggested in another response) does not.
Eric
On Thu, Oct 19, 2023 at 7:49 AM Martin Uecker wrote:
>
>
>
>
> GCC supports this as an extension.
>
> Mixing declarations and code is a
mplain about the declaration of
variables (a, b, and c) within the case statements. When I run "gcc
-Wall t.c" I get no warnings. When I run "g++ -Wall t.c" I get
warnings and errors as expected. I do get warnings when using MinGW on
Windows (gcc version 6.3 specifically). Did something change in 13.2?
Eric
On Thu, Sep 7, 2023 at 1:28 PM David Malcolm wrote:
> On Mon, 2023-09-04 at 22:13 -0400, Eric Feng wrote:
>
> > Hi Dave,
>
> Hi Eric, thanks for the patch.
>
> >
> > Recently I've been working on symbolic value support for the reference
> > count chec
Hi Dave,
Recently I've been working on symbolic value support for the reference
count checker. I've attached a patch for it below; let me know it looks
OK for trunk. Thanks!
Best,
Eric
---
This patch enhances the reference count checker in the CPython plugin by
adding support fo
Thank you for the patch!
On Fri, Sep 1, 2023 at 10:51 AM David Malcolm wrote:
>
> On Fri, 2023-09-01 at 04:49 +0200, Hans-Peter Nilsson wrote:
> > (Looks like this was committed as r14-3580-g597b9ec69bca8a)
> >
> > > Cc: gcc@gcc.gnu.org, gcc-patc...@gcc.gnu.org, Eric F
On Thu, Aug 31, 2023 at 4:19 PM David Malcolm wrote:
>
> On Thu, 2023-08-31 at 15:09 -0400, Eric Feng wrote:
> > On Thu, Aug 31, 2023 at 1:01 PM David Malcolm
> > wrote:
> > >
> > > On Wed, 2023-08-30 at 18:15 -0400, Eric Feng wrote:
>
> [...]
>
>
On Thu, Aug 31, 2023 at 1:01 PM David Malcolm wrote:
>
> On Wed, 2023-08-30 at 18:15 -0400, Eric Feng wrote:
> > On Tue, Aug 29, 2023 at 5:14 PM David Malcolm
> > wrote:
> > >
> > > On Tue, 2023-08-29 at 13:28 -0400, Eric Feng wrote:
> > > > Addi
On Tue, Aug 29, 2023 at 5:14 PM David Malcolm wrote:
>
> On Tue, 2023-08-29 at 13:28 -0400, Eric Feng wrote:
> > Additionally, by using the old model and the pointer per your
> > suggestion,
> > we are able to find the representative tree and emit a more accurate
> >
.
I've attached the patch for this (on top of the previous one) below. If
it also looks good, I can merge it with the last patch and push it in at
the same time.
Best,
Eric
---
gcc/analyzer/region-model.cc | 3 +-
gcc/analyzer/region-model.h | 7 ++--
.../g
On Tue, Aug 29, 2023 at 12:32 AM Eric Feng wrote:
>
> Hi Dave,
>
> Thanks for the feedback. I've addressed the changes you mentioned in
> addition to adding more test cases. I've also taken this chance to
> split the test files according to known function subclasses, a
e analyzer, I've done a
bootstrap and regtested the patch as well. Does it look OK for trunk?
Best,
Eric
---
This patch introduces initial support for reference count checking of
PyObjects in relation to the Python/C API for the CPython plugin.
Additionally, the core analyzer underwent several m
e necessary, but I haven't delved too
deeply into this yet,
so my suspicion could be off. Additionally, I think it would be helpful to show
users what the
ob_refcnt looks like in each event as well. I'll keep you updated on both these
points and welcome any feedba
On Wed, Aug 23, 2023 at 7:16 PM David Malcolm wrote:
>
> On Wed, 2023-08-23 at 17:15 -0400, Eric Feng wrote:
> > On Mon, Aug 21, 2023 at 11:04 AM David Malcolm
> > wrote:
> > >
> > > On Mon, 2023-08-21 at 10:05 -0400, Eric Feng wrote:
> > > > Hi D
On Mon, Aug 21, 2023 at 11:04 AM David Malcolm wrote:
>
> On Mon, 2023-08-21 at 10:05 -0400, Eric Feng wrote:
> > Hi Dave,
> >
> > Just wanted to give you and everyone else a short update on how
> > reference count checking is going — we can now observe the refcn
;
| |
| | |
| | (4) here
|
I will fix up and refactor the logic for counting the actual ref count
before coming back and refining the diagnostic to give much more
detailed information.
Best,
Eric
On Wed, Aug 16, 2023 at 9:47 PM Eric Feng wrote
Hi Dave,
Thanks for the feedback!
On Wed, Aug 16, 2023 at 5:29 PM David Malcolm wrote:
>
> On Wed, 2023-08-16 at 15:17 -0400, Eric Feng via Gcc wrote:
> > Hi everyone,
>
> [fixing typo in my email address]
>
> Hi Eric, thanks for the update, and the WIP patch.
>
>
o address the refinements necessary mentioned above.
For those interested, I've attached a WIP patch that highlights the specific
changes mentioned above.
Best,
Eric
gcc/analyzer/ChangeLog:
* region-model.cc (region_model::pop_frame): New callback
* mec
g blocks of 8 spaces with tabs
(which is a requirement in check_GNU_style). In combination, this
works for everything except for header files for some reason, but I'll
defer that battle to another day.
On Fri, Aug 11, 2023 at 1:47 PM Eric Feng wrote:
>
> Thanks for the feedback! I'
after rebase, the patch has now been pushed.
Best,
Eric
---
This patch adds known function subclasses for Python/C API functions
PyList_New, PyLong_FromLong, and PyList_Append. It also adds new
optional parameters for
region_model::get_or_create_region_for_heap_alloc, allowing for the
newly allo
gic in the revision and the only changes
within the analyzer core are changing variable names, is it OK for
trunk. In the mean time, the revised patch is currently going through
bootstrap and regtest process.
Best,
Eric
---
This patch adds known function subclasses for Python/C API functions
dg-require-python-h.
Best,
Eric
>
> > > >
> > > > Maybe someone else on the list can see a less hackish way to get
> > > > this
> > > > to work?
> > &
On Fri, Aug 4, 2023 at 6:46 PM David Malcolm wrote:
>
> On Fri, 2023-08-04 at 18:42 -0400, David Malcolm wrote:
> > On Fri, 2023-08-04 at 16:48 -0400, Eric Feng wrote:
> > > On Fri, Aug 4, 2023 at 11:39 AM David Malcolm
> > > wrote:
> > > >
> >
On Fri, Aug 4, 2023 at 11:39 AM David Malcolm wrote:
>
> On Fri, 2023-08-04 at 11:02 -0400, Eric Feng wrote:
> > Hi Dave,
> >
> > Tests related to our plugin which depend on Python-specific
> > definitions have been run by including /* { dg-options "-fan
e in gil.h?
Best,
Eric
On Tue, Aug 1, 2023 at 1:06 PM David Malcolm wrote:
>
> On Tue, 2023-08-01 at 09:57 -0400, Eric Feng wrote:
> > >
> > > My guess is that you were trying to do it from the
> > > PLUGIN_ANALYZER_INIT
> > > hook rather than from the
ER_INIT hook and not from the plugin_init
function. After following your suggestion, the callbacks are getting
registered as expected. I submitted a patch to review for this feature
on gcc-patches; please let me know if it looks OK.
Best,
Eric
tation fault when trying to call the lookup functions within
translation_unit at the time of plugin initialization, even though the
translation unit is stored correctly. So it seems like the solution
may not be quite so simple.
I'm currently investigating this issue, but if there's an obvious
solution that I might be missing or any general suggestions, please
let me know!
Thanks as always,
Eric
achine isn't transitioning the pointer from "start" to "assumed-
> non-null". Such state machine states inhibit state-merging, and so
> this might solve your state-merging problem.
>
> I think we need a way to call malloc_state_machine::on_allocator_call
> from outside of sm-malloc.cc. See region_model::on_realloc_with_move
> for an example of how to do something similar.
>
Thank you for the suggestion — this worked great and has solved the issue!
Best,
Eric
ations. For instance:
PyObject* foo() {
PyObject item = PyLong_FromLong(10);
PyObject list = PyList_New(5);
PyList_Append(list, item);
return list;
}
The above scenario is simulated as expected. I will continue to search
for a solution, but any suggestions would be highly appreciated. Thank
you!
Best,
Eric
On Wed, Jul 5, 2023 at 7:28 AM Jonathan Wakely via Gcc wrote:
>
> On Wed, 5 Jul 2023 at 12:01, Julian Waters via Gcc wrote:
> >
> > I see, thanks Andrew.
> >
> > Anyone else have opinions on this besides Liu or Andrew? The responses have
> > been surprisingly quiet thus far
>
> IMHO all warnings
check out the repo at
https://github.com/efric/gcc-cpython-analyzer for details on the
project and to follow along and help out where you are interested.
Best,
Eric
On Tue, Jun 27, 2023 at 6:03 AM Steven Sun wrote:
>
> Hi Eric, I am Steven (now) from the CPython team.
>
> How is
ich tree is the PyObject RECORD_TYPE before the frontend is
> cleaned up (in on_finish_translation_unit).
Sounds good, I will look into that. Thanks for the suggestion!
Best,
Eric
On Wed, Jun 7, 2023 at 5:55 PM David Malcolm wrote:
>
> On Wed, 2023-06-07 at 16:21 -0400, Eric Feng wrote:
&g
Please let me know if this
approach makes sense and if so where I could look into to get the
required information.
Thanks all.
Best,
Eric
zation if -fno-delete-dead-exceptions is not specified).
--
Eric Botcazou
On 5/15/23, Richard Earnshaw (lists) via Gcc wrote:
> On 10/05/2023 03:38, Eli Zaretskii via Gcc wrote:
>>> From: Arsen Arsenović
>>> Cc: Eli Zaretskii , Jakub Jelinek ,
>>> jwakely@gmail.com, gcc@gcc.gnu.org
>>> Date: Tue, 09 May 2023 22:21:03 +0200
>>>
The concern is using the good w
On 5/9/23, Jonathan Wakely via Gcc wrote:
> On Tue, 9 May 2023 at 23:38, Joel Sherrill wrote:
>> We are currently using gcc 12 and specifying C11. To experiment with
>> these stricter warnings and slowly address them, would we need to build
>> with a newer C version?
>
> No, the proposed changes
s
not on x86[_64]/Linux where you *cannot* probe below the stack pointer.
--
Eric Botcazou
On Fri, Apr 21, 2023 at 10:27:18PM +0200, Alejandro Colomar wrote:
> Link: <https://austingroupbugs.net/view.php?id=1641>
> Reported-by: Bastien Roucariès
> Reported-by: Alejandro Colomar
> Reviewed-by: Eric Blake
> Cc: glibc
> Cc: GCC
> Cc: Stefan Puiu
> Cc:
oids the UB).
> +without invoking Undefined Behavior (UB).
> +POSIX Issue 8 will fix this by requiring that implementations
> +make sure that these structures
> +can be safely used as they were designed.
> .SH NOTES
> .I socklen_t
> is also defined in
>
>
> I guess this is simple enough that it should work as documentation.
It seems fine from my perspective.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
> I'm assuming the problem also extends to the other __gthr_win32 routines as
> well, __gthr_win32_create just happens to be the first symbol it cannot
> find.
>
> Is there a way to fix this issue?
How did you configure the compiler and what version of MinGW64 do you use?
--
Eric Botcazou
On Wed, Apr 05, 2023 at 02:42:04AM +0200, Alejandro Colomar wrote:
> Hi Eric,
>
> I'm going to reply both your emails here so that GCC is CCed, and they can
> suggest better stuff. I'm worried about sending something to POSIX without
> enough eyes checking it. So
Thanks Martin! Sounds good; I submitted my proposal unchanged for now
(i.e assuming an independent project), but as Dave mentioned in
another thread, it may be divided into several logical components,
perhaps with certain features extended, to be suited for
collaboration.
Best,
Eric
On Mon
these smaller tasks
first to be more efficient in tackling the more involved tasks
anyways. It would also be easy to divvy these tasks up as well.
Best,
Eric
Thanks for bringing this to my attention Dave! I’m happy to
collaborate on this project with Steven. I will reply in more detail
in the other thread.
Best,
Eric
On Sun, Apr 2, 2023 at 7:28 PM David Malcolm wrote:
>
> On Sat, 2023-04-01 at 19:49 -0400, Eric Feng wrote:
> > > For
checking, errors in exception handling,
and verification of PyMethodDef tables
___
Thank you!
Best,
Eric
On Tue, Mar 28, 2023 at 3:14 PM David Malcolm wrote:
>
> On Tue, 2023-03-28 at 08:08 -0400, Eric Feng wrote:
> > My apologies. Forgot to CC the mailing list in my previous e-
: gdb has a song: https://www.gnu.org/music/gdb-song.en.html
Perhaps GCC could have a song as well?
Anyways, just some fun food for thought on this day of foolishness;
please don't take these suggestions too seriously (unless you want
to).
Happy hacking!
Eric Gallager
er
> that aliasing it is safe (suggesting a unnamed union, or other compiler
> magic).
>
> Link: <https://www.austingroupbugs.net/view.php?id=1641>
> Reported-by: Bastien Roucariès
> Reported-by: Alejandro Colomar
> Cc: glibc
> Cc: GCC
> Cc: Eric Blake
> Cc: Stef
ou clarify by giving an example of what
the new attributes you had in mind might look like and how they would
help (for example with respect to reference counting semantics)?
Incidentally, I forgot to mention in my previous email but I believe
the 350-hour option is the one that is more appropriate fo
nd solve them on behalf of the
compiler. This project is still in its early stages, but the idea is
to delegate type inference functionalities to a generic library given
some information instead of having to write your own constraint
solver.
___
Thank you for reviewing my proposal!
Best,
Eric Feng
> rs6000 indeed doesn't implement {,u}{add,sub,mul}v4_optab for
> any mode and thus leaves it to the generic code.
https://gcc.gnu.org/pipermail/gcc-patches/2016-October/460209.html
--
Eric Botcazou
he Austin Group on your
behalf to get the POSIX wording improved, I think it would work better
if you initiate a bug report rather than having me do it:
https://www.austingroupbugs.net/main_page.php
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
,
but I'll catch up to you guys eventually :)
So at least we know for sure that this particular instance of extra
characters is coming from Wine. Maybe Wine can be smart enough to
only translate \n into \r\n instead of translating \r\n into \r\r\n.
Jacek / Eric, comments here? I'm happy t
not cover
the basic block containing insn 14 and 15?
--
Eric Botcazou
:DI 34)
> (pc))) "bad_cc.c":12:10 15 {condjump}
> (expr_list:REG_DEAD (reg:CC 66 cc)
> (int_list:REG_BR_PROB 365072228 (nil)))
> -> 34)
>
> Please observe the REG_DEAD note on the both jump instructions.
Passes that consume REG_DEAD/REG_UNUSED notes need to recompute them
explicitly, they are not updated on the fly.
--
Eric Botcazou
> So what could be causing it?
An oversight in https://gcc.gnu.org/pipermail/gcc-cvs/2022-August/370830.html
has broken --disable-sjlj-exceptions. That's now fixed.
--
Eric Botcazou
On Fri, Aug 19, 2022 at 6:13 AM Jonas Rahlf via Gcc wrote:
>
> As a firmware developer I would appreciate a warning option about padding
> bytes, but only for such cases where you can reduce the number of padding
> bytes by rearranging the fields.
>
> The current -Wpadded warns about all padding b
On Thu, Jun 23, 2022 at 12:25 AM Bruno Haible wrote:
>
> Iain Sandoe wrote:
> > Yes (
> > # We can use an in-tree build of libintl.
> > if test -f ifelse([$1],,[../gettext-runtime],[$1])/uninstalled-config.sh;
> > then
> >
> > relative_builddir='ifelse([$1],,[${top_builddir}/..],[$1]/..)/gett
recommended combination with recent versions
of the compiler, but Solaris ld must be recent enough, otherwise building for
sparc-sun-solaris2.11 probably does not work indeed.
--
Eric Botcazou
rogram (deprecated since 2010) is
> no longer available. Instead of including the intl sources in your
> package, we suggest making the libintl library an optional prerequisite
> of your package. This will simplify the build system of your package.
> - Accordingly,
On Sun, Jun 12, 2022 at 12:38 PM David Malcolm via Gcc wrote:
>
> On Sat, 2022-06-11 at 02:35 +0200, Eric Botcazou wrote:
> > > Hope this is helpful; please let me know if you see any mistakes,
> > > or if
> > > there's room for improvement
> >
> >
> Hope this is helpful; please let me know if you see any mistakes, or if
> there's room for improvement
Nice work! In the "inside cc1" chapter, I think that IR is usually meant for
"Intermediate Representation" rather than "Internal Representation" in this
context.
--
Eric Botcazou
On Wed, Jun 8, 2022 at 5:00 PM Miika wrote:
>
> On Wednesday, June 8th, 2022 at 8:42 PM, Eric Gallager
> wrote:
> > Could you take a look at bug 78155 too? There was a request to add
> > something like this in that bug:
> > https://gcc.gnu.org/bugzilla/show_bug.cg
ormation available.
If you try to debug at an optimization level higher than -Og, your mileage may
vary and depend on various factors; that's apparently an example where the
debug info is slightly less damaged at -O3 on x86 than on PowerPC, but there
are probably cases where this will be
On Sun, Jun 5, 2022 at 4:10 PM Miika via Gcc wrote:
>
> Based on Jakub's and Yair's comments I created a new attribute "inrange".
> Inrage takes three arguments, pos min and max.
> Pos being the argument position in the function, and min and max defines the
> range of valid integer. Both min and m
you
use with aclocal (or whatever the relative path to config is from your
current working directory).
Eric
On Wed, Apr 27, 2022 at 12:20 PM Jonathan Wakely via Gcc
wrote:
>
> On Wed, 27 Apr 2022 at 16:29, Andrea Monaco via Gcc wrote:
> >
> >
> > This program
> >
> > #include
> >
> > int main ()
> > {
> > char *s;
> > isspace (s);
> > }
> >
> > compiles with no warning in gcc 8.3.0, ev
r it in an object (SUBSTITUTE_PLACEHOLDER_IN_EXPR). You can presumably do
it through the gimplification hook.
--
Eric Botcazou
the discriminant since it is assigned in the CONSTRUCTOR, so
the gimplifier is indeed presumably not wired to eliminate them on its own.
--
Eric Botcazou
> Release managers.
They certainly have authority on the timing, but not on the contents.
> Working on that right now, sorry..
OK, thanks in advance.
--
Eric Botcazou
wrong and should be reverted ASAP.
--
Eric Botcazou
On Fri, Jan 14, 2022 at 11:14 AM Michael Matz via Gcc wrote:
>
> Hello,
>
> On Fri, 14 Jan 2022, Martin Liška wrote:
>
> > Hello.
> >
> > I'm working on a testsuite clean-up where some of the files are wrongly
> > named.
> > More precisely, so files have .cc extension and should use .C. However
On Mon, Jan 10, 2022 at 8:28 AM Iain Sandoe wrote:
>
> Hi Florian,
>
> > On 10 Jan 2022, at 08:38, Florian Weimer wrote:
> >
> > * Jeff Law via Gcc:
> >
> >> Most targets these days use registers for parameter passing and
> >> obviously we can run out of registers on all of them. The key
> >> pr
osing these hours is to debug the code at -O0.
--
Eric Botcazou
> Yes, although I think potentially trapping ops
> are not moved before calls (as this would be
> incorrect). So do you think it would be feasable
> to prevent this for volatile too?
Feasible probably, but why would this be desirable in C? It's not Java!
--
Eric Botcazou
entence is again a blatant overstatement but I agree
that the alignment caveat ought to be documented. Please suggest a wording to
that effect and post a patch onto the gcc-patches@ ML. Thanks in advance.
--
Eric Botcazou
On Wed, Nov 10, 2021 at 9:26 AM Joel Sherrill wrote:
>
> Thanks for the quick reply.
>
> On Wed, Nov 10, 2021 at 8:20 AM Jonathan Wakely wrote:
> >
> > On Wed, 10 Nov 2021 at 14:08, Joel Sherrill wrote:
> > >
> > > Hi
> > >
> > > It's been a while since I tried this and it appears things have
> >
On Tue, Sep 28, 2021 at 2:48 AM Toon Moene wrote:
>
> On 9/28/21 8:35 AM, Erick Ochoa via Gcc wrote:
>
> >> Can ubsan be used on the compiler itself?
>
> I regularly build the compiler(s) natively with ubsan enabled, see for
> instance:
>
> https://gcc.gnu.org/pipermail/gcc-testresults/2021-Septem
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
deprecations on the changes page ASAP, so that people can have time to
prepare for the impending deprecations.
Thanks,
Eric Gallager
1 - 100 of 1858 matches
Mail list logo
