[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fedora-devel-list
Subject:    Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change propo
From:       Naheem Zaffar <naheemzaffar () gmail ! com>
Date:       2022-11-09 4:26:23
Message-ID: CAMegAE2fZKi8waVe=VW1j=Q=XuoSMxGB6q=9iLjEr6keOe1+vA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Tue, 8 Nov 2022, 19:22 Vitaly Zaitsev via devel, <
devel@lists.fedoraproject.org> wrote:

> On 08/11/2022 19:53, Naheem Zaffar wrote:
> > Has there been any consideration to turn on frame pointers for atleast
> > dev releases?
>
>
> Fedora has no dev releases. Mass rebuild is a huge pain for maintainers
> due to FTBFS issues, and doing it multiple times is unacceptable.
>
I think I explained the idea poorly.

Not all builds in rawhide are release builds. You will get for instance the
whole gnome stack beta releases and rc releases during development.

This isnt limited to gnome, most software will go into rawhide first to
stabilise.

It is almost never intended for these builds to end up in the final
release  ll, but they are useful and necessary parts of the development
cycle. Theywill be replaced before general availability, all without a mass
rebuild.

It's not a silver bullet solution but atleast it starts things off on a
path where profiling can be done in a limited manner compared to the other
proposed alternatives where the tooling doesnt exist and will likely not
ever be written.

>
>

[Attachment #5 (text/html)]

<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Tue, 8 Nov 2022, 19:22 Vitaly Zaitsev via devel, &lt;<a \
href="mailto:devel@lists.fedoraproject.org">devel@lists.fedoraproject.org</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">On 08/11/2022 19:53, Naheem Zaffar \
wrote:<br> &gt; Has there been any consideration to turn on frame pointers for \
atleast <br> &gt; dev releases?<br>
<br>
<br>
Fedora has no dev releases. Mass rebuild is a huge pain for maintainers <br>
due to FTBFS issues, and doing it multiple times is \
unacceptable.<br></blockquote></div></div><div dir="auto">I think I explained the \
idea poorly.</div><div dir="auto"><br></div><div dir="auto">Not all builds in rawhide \
are release builds. You will get for instance the whole gnome stack beta releases and \
rc releases during development.</div><div dir="auto"><br></div><div dir="auto">This \
isnt limited to gnome, most software will go into rawhide first to \
stabilise.</div><div dir="auto"><br></div><div dir="auto">It is almost never intended \
for these builds to end up in the final release   ll, but they are useful and \
necessary parts of the development cycle. Theywill be replaced before general \
availability, all without a mass rebuild.</div><div dir="auto"><br></div><div \
dir="auto">It&#39;s not a silver bullet solution but atleast it starts things off on \
a path where profiling can be done in a limited manner compared to the other proposed \
alternatives where the tooling doesnt exist and will likely not ever be \
written.</div><div dir="auto"><div class="gmail_quote"><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">  <br> </blockquote></div></div></div>


[Attachment #6 (text/plain)]

_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue


[prev in list] [next in list] [prev in thread] [next in thread]