[Bug lto/49697] New: read permission of LTO intermediate files

[Bug lto/49697] New: read permission of LTO intermediate files

[Joost.VandeVondele at pci dot uzh.ch]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49697

           Summary: read permission of LTO intermediate files
           Product: gcc
           Version: 4.6.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: lto
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: Joost.VandeVondele@pci.uzh.ch


not sure if this is a bug, but LTO generates intermediate files in $TMPDIR that
are readable by all

-rw-r--r--   cleUTZi.ltrans17.ltrans.o

instead of the usual -rw------- for other gcc files that appear in $TMPDIR

[Bug lto/49697] read permission of LTO intermediate files

[rguenth at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49697

--- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-07-11 09:26:31 UTC ---
It uses your umask, similar to what it uses for the generated assembly.

[Bug lto/49697] read permission of LTO intermediate files

[rguenth at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49697

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2012-05-07
     Ever Confirmed|0                           |1

--- Comment #2 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-05-07 12:37:52 UTC ---
Confirmed at least.

[Bug lto/49697] read permission of LTO intermediate files

[pinskia at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49697

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pinskia at gcc dot gnu.org

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
  lo->fd = open (fname,
                 (writable
                  ? O_WRONLY | O_CREAT | O_BINARY
                  : O_RDONLY | O_BINARY),
                 0666);

Every other file that gets created by GCC is fopen which according to the man
page:
       Any created file will have the mode S_IRUSR | S_IWUSR | S_IRGRP |
S_IWGRP | S_IROTH | S_IWOTH (0666), as modified by the process's umask value
(see umask(2)).


I would assume umask modifies open's mode too ...

Let me try to dig into this slightly more tomorrow.