self hosted compiler: avoid Dir.realpathAlloc

The use of Dir-related realpath functions will put std.os.getFdPath in
the critical path which makes the compiler less portable.

Author: mikdusan

src/Compilation.zig

@@ -4064,12 +4064,17 @@ fn updateCObject(comp: *Compilation, c_object: *CObject, c_obj_prog_node: *std.P
             );
 
             const args_dir = "args";
-            try output_dir.handle.makePath(args_dir);
-            const args_file = try fs.path.join(allocator, &[_][]const u8{
-                args_dir, args_hex_hash[0..],
-            });
-            try output_dir.handle.writeFile(args_file, args);
-            const args_file_path = try output_dir.handle.realpathAlloc(allocator, args_file);
+            const args_file_path = args_file_path: {
+                if (output_dir.path) |odp| {
+                    break :args_file_path try fs.path.join(allocator, &[_][]const u8{
+                        odp, args_dir, args_hex_hash[0..],
+                    });
+                } else {
+                    break :args_file_path try fs.path.join(allocator, &[_][]const u8{
+                        args_dir, args_hex_hash[0..],
+                    });
+                }
+            };
 
             argv.shrinkRetainingCapacity(2);
             try argv.append(try std.mem.concat(allocator, u8, &[_][]const u8{ "@", args_file_path }));