public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: <sundeep.kokkonda@gmail.com>
To: "'Andrew Pinski'" <pinskia@gmail.com>
Cc: "'GCC Patches'" <gcc-patches@gcc.gnu.org>
Subject: RE: [PATCH] Fix for GCC '-MF' option cannot deal with long paths in Windows
Date: Fri, 4 Feb 2022 09:29:59 +0530	[thread overview]
Message-ID: <04ea01d8197b$af2d4100$0d87c300$@gmail.com> (raw)
In-Reply-To: <003501d80cf2$c1ab0820$45011860$@gmail.com>

Hello Andrew,

Can you please let me know your feedback on the patch?


Thanks,
Sundeep K.

-----Original Message-----
From: sundeep.kokkonda@gmail.com <sundeep.kokkonda@gmail.com> 
Sent: Wednesday, January 19, 2022 10:40 AM
To: 'Andrew Pinski' <pinskia@gmail.com>
Cc: 'GCC Patches' <gcc-patches@gcc.gnu.org>
Subject: RE: [PATCH] Fix for GCC '-MF' option cannot deal with long paths in Windows

Hello Andrew,

I updated the patch. Please see attached patch files and let me know your feedback.



Thanks,
Sundeep K.

-----Original Message-----
From: Andrew Pinski <pinskia@gmail.com>
Sent: Tuesday, January 18, 2022 9:22 AM
To: sundeep.kokkonda@gmail.com
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix for GCC '-MF' option cannot deal with long paths in Windows

On Mon, Jan 17, 2022 at 8:35 AM Sundeep KOKKONDA via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>
> Hello,
>
>
>
> The '-MF' option cannot deal with path size >256 characters in 
> Windows. This patch is to fix this long path issue with -MF option.
>
> Let me know is it ok to commit?

I don't think this is the right place to put this.
Maybe a better way to implement this is to have a wrapper around fopen for windows and do it that way.
Does open have the same issue?

Thanks,
Andrew Pinski

>
>
>
>
>
> --
>
> Thanks,
>
> Sundeep K.
>


  reply	other threads:[~2022-02-04  4:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-17 16:32 sundeep.kokkonda
2022-01-18  3:51 ` Andrew Pinski
2022-01-19  5:09   ` sundeep.kokkonda
2022-02-04  3:59     ` sundeep.kokkonda [this message]
2022-02-22  5:21       ` sundeep.kokkonda

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='04ea01d8197b$af2d4100$0d87c300$@gmail.com' \
    --to=sundeep.kokkonda@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=pinskia@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).