Re: [PATCH v1 05/13] Reuse MinGW from i386 for AArch64
On Sun, 25 Feb 2024 at 22:12, Mark Harmstone wrote: > Also, there are relocation types needed for Windows programs that are > supported in COFF but not in ELF object files. > Right, it's been a long time since i last dealt with PECOFF and i had assumed that things might have changed in the meantime. PS: Please don't forget to add an entry to contrib/config-list.mk thanks
Re: [PATCH v1 05/13] Reuse MinGW from i386 for AArch64
On 22/2/24 11:11, Richard Earnshaw (lists) wrote: Most of the free world has left COFF behind since several decades, so I won't comment on that. YMMV. This isn't helpful. Windows platforms use (a derivative of) COFF, so that's what the tools need to use when targetting that platform. Also, there are relocation types needed for Windows programs that are supported in COFF but not in ELF object files. Mark
Re: [PATCH v1 05/13] Reuse MinGW from i386 for AArch64
On Thu, 22 Feb 2024 15:56:46 +
Evgeny Karpov wrote:
> A ChangeLog template using "Moved... ...here" has been generated by
> contrib/mklog.py.
> It seems that it needs modification.
>
> Regards,
> Evgeny
>
> -Original Message-
> Thursday, February 22, 2024 12:11 PM
> Richard Earnshaw (lists) wrote:
>
> > The ChangeLog has to be expressed in present tense, as mandated by the
> > standard; s/Moved/Move/g etc.
>
> Agreed, but that's a detail that we can get to once the patch has been
> properly reviewed.
>
Excellent, two patches for the price of one :)
diff --git a/contrib/mklog.py b/contrib/mklog.py
index d764fb41f99..7d8d554b15e 100755
--- a/contrib/mklog.py
+++ b/contrib/mklog.py
@@ -277,7 +277,7 @@ def generate_changelog(data, no_functions=False,
fill_pr_titles=False,
# it used to be path.source_file[2:]
relative_path = get_rel_path_if_prefixed(file.source_file[2:],
changelog)
-out = append_changelog_line(out, relative_path, 'Moved to...')
+out = append_changelog_line(out, relative_path, 'Move to...')
new_path = get_rel_path_if_prefixed(file.target_file[2:],
changelog)
out += f'\t* {new_path}: ...here.\n'
cheers
Re: [PATCH v1 05/13] Reuse MinGW from i386 for AArch64
On Thu, 22 Feb 2024, Richard Earnshaw (lists) wrote: > On 21/02/2024 21:34, rep.dot@gmail.com wrote: > > On 21 February 2024 19:34:43 CET, Evgeny Karpov > > wrote: > >> > > > > Please use git send-email. Your mail ends up as empty as here, otherwise. > > I don't see anything wrong with it; niether does patchwork > (https://patchwork.sourceware.org/project/gcc/list/?series=31191) nor > does the Linaro CI bot. So perhaps it's your mailer that's > misconfigured. The first part of the multipart/mixed message is empty (well, two blank lines). The second part, the patch, has Content-Disposition: attachment, so it's correct for a mailer not to show it inline (instead showing an empty message with an attachment - which is how it appeared to me). -- Joseph S. Myers josmy...@redhat.com
Re: [PATCH v1 05/13] Reuse MinGW from i386 for AArch64
On 21/02/2024 21:34, rep.dot@gmail.com wrote: > On 21 February 2024 19:34:43 CET, Evgeny Karpov > wrote: >> > > Please use git send-email. Your mail ends up as empty as here, otherwise. I don't see anything wrong with it; niether does patchwork (https://patchwork.sourceware.org/project/gcc/list/?series=31191) nor does the Linaro CI bot. So perhaps it's your mailer that's misconfigured. > > The ChangeLog has to be expressed in present tense, as mandated by the > standard; s/Moved/Move/g etc. Agreed, but that's a detail that we can get to once the patch has been properly reviewed. > > In any sane world ( and in gcc ) to fold, respectively a folder, is something > else compared to a directory ( which you probably mean when moving a file > from one directory to another directory as you seem to do ). > > Most of the free world has left COFF behind since several decades, so I won't > comment on that. YMMV. This isn't helpful. Windows platforms use (a derivative of) COFF, so that's what the tools need to use when targetting that platform. R.
Re: [PATCH v1 05/13] Reuse MinGW from i386 for AArch64
On 21 February 2024 19:34:43 CET, Evgeny Karpov wrote: > Please use git send-email. Your mail ends up as empty as here, otherwise. The ChangeLog has to be expressed in present tense, as mandated by the standard; s/Moved/Move/g etc. In any sane world ( and in gcc ) to fold, respectively a folder, is something else compared to a directory ( which you probably mean when moving a file from one directory to another directory as you seem to do ). Most of the free world has left COFF behind since several decades, so I won't comment on that. YMMV. HTH
Re: [PATCH v1 05/13] Reuse MinGW from i386 for AArch64
On Wed, Feb 21, 2024 at 10:38 AM Evgeny Karpov wrote: > > In config/i386/winnt.cc there are many x86_64 comments and many function names that use i386 in them? When moving it seems like better to rename them and remove references to 86. I don't see any changes that rename the functions or comments there. Thanks, Andrew
