Non-parallel build can fail, depending on the ./configure parameters -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106472 .
The change below does fix the problem.
I do not understand the build system to say, that this is the best
approach, so if there are questions I might or might not be abl
with a
comment, indicating the quality of the patch. The change proposed by me does
fix PR106472.
Kind regards
Дилян
-Original Message-
From: Jakub Jelinek
Reply-To: Jakub Jelinek
To: Дилян Палаузов , Paolo Bonzini
, Nathanael Nerode , Alexandre Oliva
, Ralf Wildenhues , Ian Lance
ян
Am 25. März 2024 23:59:52 UTC schrieb Ian Lance Taylor :
>On Sat, Mar 23, 2024 at 4:32 AM Дилян Палаузов
> wrote:
>>
>> Can the build experts say what needs to be changed? The dependencies I
>> added are missing in the build configuration (@if gcc-bootstrap).
>>
&
x-gnu directory?
Kind regards Дилян
Am 26. März 2024 16:37:40 UTC schrieb Ian Lance Taylor :
>On Tue, Mar 26, 2024 at 9:33 AM Дилян Палаузов
> wrote:
>>
>> Makefile.def contains already:
>>
>> host_modules= { module= libbacktrace; bootstrap=true; }; // since eff02e4f84
Hello,
on 27th October I sent to gcc-patches a mail with the subject “Don’t
build gdb/readline/libreadline.a, when --with-system-readline is
supplied” and on 14th November I sent a reminder. I got no answer.
Before sending the emails I filled a bugzilla ticket.
Can you please make it clear, whe
Hello,
will it help, if Bugzilla is reprogrammed to send automatically weekly
reminders on all patches, that are not integrated yet?
Will lt help, if I hire myself to integrate the patch, or shall I
rather hire somebody to send reminders?
If something can be done after sending a reminder, then i
Hello,
what shall happen, so that no reminders are necessary to move things
forward? Why does sending a reminder make a difference and are only
penetrant persons blessed?
Regards
Дилян
On Fri, 2018-12-07 at 10:55 +, Дилян Палаузов wrote:
> Hello,
>
> will it help, if Bu
Building GDB always builds the bundles libreadline.a, even if use of
the libreadline installed on the system was requested with --with-
system-readline.
The change below is for binutils-gdb’s/configure.ac, which is
maintained by gcc.
See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87741 [GCC] a
Forwarded Message
From: Дилян Палаузов
To: gcc-patches@gcc.gnu.org
Subject: Don’t build gdb/readline/libreadline.a, when --with-system-
readline is supplied
Date: Sat, 27 Oct 2018 19:53:44 +
Building GDB always builds the bundled libreadline.a, even if use of
the
given to submitters who send reminders, irrespective of
the properties a patch has.
Regards
Дилян
On Mon, 2019-02-11 at 10:22 -0600, Segher Boessenkool wrote:
> On Mon, Feb 11, 2019 at 02:16:27PM +0000, Дилян Палаузов wrote:
> > Hello Segher,
> >
> > my question was
Hello Segher,
On Sun, 2019-02-17 at 13:09 -0600, Segher Boessenkool wrote:
> On Sun, Feb 17, 2019 at 04:59:40PM +0000, Дилян Палаузов wrote:
> > My point is to reorgnize the approach in such a way, that sending reminders
> > gets irrelevant (has no impact) and
> > th
… by applying
sed -i "s/the the/the/" `git grep -l "the the"`
.
Regards
Дилян
On Fri, 2018-12-07 at 10:55 +, Дилян Палаузов wrote:
> Hello,
>
> will it help, if Bugzilla is reprogrammed to send automatically weekly
> reminders on all patches, that are not integrated yet?
>
> Will lt help, if I hire myself to integrate the patch, or sha
:55:11AM +0000, Дилян Палаузов wrote:
> > will it help, if Bugzilla is reprogrammed to send automatically weekly
> > reminders on all patches, that are not integrated yet?
>
> No, that will not help.
>
> If an interested party sends a friendly ping, that is of course wel
d over website over a mailing list.
Regards
Дилян
On Sun, 2019-02-10 at 14:56 -0600, Segher Boessenkool wrote:
> Hi Dilyan,
>
> On Sun, Feb 10, 2019 at 02:45:02PM +, Дилян Палаузов wrote:
> > Do you share the opinion, that whatever can be done after receiving a
> > remin
sending
reminders, is a good idea. This saves time
of people to write reminders.
Greetings
Дилян
On Mon, 2019-02-11 at 07:57 -0600, Segher Boessenkool wrote:
> On Mon, Feb 11, 2019 at 12:44:31PM +0000, Дилян Палаузов wrote:
> > -- at https://www.gnu.org/software/gcc/contribute.html is wr
-
From: Jakub Jelinek
Reply-To: Jakub Jelinek
To: Дилян Палаузов
Cc: Andrew Pinski , gcc-patches@gcc.gnu.org
Subject: Re: Why -Wsuggest-attribute=noreturn does not apply to static?
Date: 07/10/24 11:43:24
On Mon, Oct 07, 2024 at 10:21:05AM +0300, Дилян Палаузов wrote:
> do you mean t
Hello,
https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wsuggest-attribute_003d
says for -Wsuggest-attribute=noreturn:
> The compiler only warns for functions visible in other compilation units.
Why? clang -Wmissing-noreturn does warn even for static functions.
Greetings
Дилян
e same
TU? Do the [[noreturn]] optimizations still apply?
What happens to a static [[noreturn]] function, if a pointer to it is passed to
other TU and that other TU calls the function?
Greetings
Дилян
-Original Message-
From: Andrew Pinski
To: Дилян Палаузов
Cc: gcc-patches@gcc.gnu.o
19 matches
Mail list logo
