On Mon, Dec 5, 2022 at 5:48 AM Randy MacLeod
<[email protected]> wrote:
>
> Let's keep the discussion on the list to give everyone a chance to know 
> what's going on and to contribute.
> Oh and please use in-line email instead of attachments when possible.
>
> Also add Khem who is the author of many of these patches. Hopefully he can
> help us clean-up the status and advise about which 'Pending' patches are
> candidates to send upstream.
>
> On 2022-12-05 08:06, Shinde, Yash wrote:
>
> Hi Richard,
>
> PFA  document for GCC patch analysis. There were about 28 patches in GCC 
> sources out of which 3 patches are with the upstream status of ‘Submitted’ 
> and other 10 are ‘Pending’.  I had analysed the current status of these 
> patches by checking them with the GCC patch list and archive list and 
> documented the same in the attached document.
>
> Out of the 3 patches with ‘submitted’ as the status,
>
> - The 1st patch is submitted but changes are not reflected in the upstream. 
> (hardcoded-paths.patch)
>
> - The 2nd patch is not found in the upstream 
> (0014-Don-t-search-host-directory-during-relink-if-inst_pr.patch), was not 
> found in patch list or archive list and
>
> - For the 3rd patch 1 hunk taken to upstream and can be marked as 
> 'backported' and the other hunk is not taken to upstream yet. 
> (prefix-map-realpath.patch)

Did you check upstream master branch of gcc ?

>
> All the patch links are given in the doc.
>
>
> GCC 12.2 Patch Analysis
>
> hardcoded-paths.patch:Upstream-Status: Submitted 
> [https://gcc.gnu.org/pipermail/gcc-patches/2022-August/599882.html]
> ->Patch is submitted but changes not reflected in upstream
>
>
>
> 0014-Don-t-search-host-directory-during-relink-if-inst_pr.patch:Upstream-Status:
>  Submitted
> ->not yet submitted to upstream but link provided here- 
> http://lists.gnu.org/archive/html/libtool-patches/2011-01/msg00026.html
>
> prefix-map-realpath.patch:Upstream-Status: Submitted 
> [https://gcc.gnu.org/pipermail/gcc-patches/2022-August/599885.html]
> ->1 of the 2 hunks of patch send to upstream and other is not included. Link- 
> https://www.mail-archive.com/[email protected]/msg294480.html
>
> 0013-Ensure-target-gcc-headers-can-be-included.patch:Upstream-Status: Pending
> ->not yet submitted to upstream
>
> 0005-Use-the-defaults.h-in-B-instead-of-S-and-t-oe-in-B.patch:Upstream-Status:
>  Pending
> ->not yet submitted to upstream
>
> 0004-Pass-CXXFLAGS_FOR_BUILD-in-a-couple-of-places-to-avo.patch:Upstream-Status:
>  Pending [should be submittable]
> ->not yet submitted to upstream
>
> 0002-gcc-poison-system-directories.patch:Upstream-Status: Pending
> ->not yet submitted to upstream
>
> 0009-gcc-armv4-pass-fix-v4bx-to-linker-to-support-EABI.patch:Upstream-Status: 
> Pending
> ->not yet submitted to upstream
>
> 0017-Search-target-sysroot-gcc-version-specific-dirs-with.patch:Upstream-Status:
>  Pending
> ->not yet submitted to upstream
>
> 0008-libtool.patch:Upstream-Status: Pending
> ->not yet submitted to upstream
>
> 0020-libgcc_s-Use-alias-for-__cpu_indicator_init-instead-.patch:Upstream-Status:
>  Pending
> ->not yet submitted to upstream
>
> 0018-Add-ssp_nonshared-to-link-commandline-for-musl-targe.patch:Upstream-Status:
>  Pending
> ->not yet submitted to upstream
>
> 0006-cpp-honor-sysroot.patch:Upstream-Status: Pending
> ->not yet submitted to upstream
>
>
>
>
> For the patches with ‘pending’ as the status, they are pending from quite 
> some time. Should we contact the author of the patch or the community for 
> these patches?
>
> Please guide me on how to proceed further in GCC patch analysis and what are 
> the next steps.
>
> Let's see what Khem has to say about his collection of 'Pending' patches.
>
>
> Thanks Yash,
>
> ../Randy
>
>
> Regards,
> Yash Shinde
>
>
>
>
>
>
> --
> # Randy MacLeod
> # Wind River Linux
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#174295): 
https://lists.openembedded.org/g/openembedded-core/message/174295
Mute This Topic: https://lists.openembedded.org/mt/95468728/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to